I just joined and I suspect that you're correct: there's an overall learning curve. No snarky tone intended, but explaining decentralization to those who would likely struggle with grasping the basic client/server model is going to be challenge.
Shoot, I've got 10 years pentesting and R&D under my belt and it took me a while to weigh the pros and cons of creating an account on a public instance or self-hosting. (Will self-host eventually...enjoying a test drive.)
Definitely complicated to root cause. Please share if ya figure out the hard parts ๐
An idea: Netflix could be fingerprinting TUN interfaces on the TV.
One thing I'd consider trying is Tailscale in userspace networking mode on a distinct network host at location 2, which'll start a SOCKS/HTTP proxy that the TV can use for outbound connections.
Bonus: any devices incompatible with Tailscale can use the proxies.
If you'd like to take a stab at this, Headscale is a self-hosted version of Tailscale's service. Personally, I use Caddy to automatically manage letsencrypt certs while proxying requests to Headscale.