401s are because you’re not signed in on Twitch (expected), postMessage error is because the embed is not on twitch.tv (expected). The stack traces could be real problems, but if everything works, they can be ignored.
A cross-origin iframe cannot mess with JS on the parent page unless the browser isn’t properly restricting cross-origin access (usually due to insecure configuration or significantly outdated browser).