Well, the good news is that as an end-user you'll probably only have one monolithic proprietary chunk of code that's even conveniently integrated into your web browser. The bad news is that you'll have to hope that all the DRMed video sites you're using support the proprietary scheme your particular browser and platform use. In this case, it's Microsoft's PlayReady DRM.
Also, the codec used is actually part of the proprietary blob, and there are no requirements as to which codecs or containers a particular DRM scheme supports, so in theory every DRM scheme could require a different, incompatible proprietary codec and they'd still all be 100% standards compliant.
There is also no reason to think that these binary blobs will be built for platforms that the video providers have not given two shits about in the past. Anyone who is supporting this stuff because they think it will get them Netflix on a GNU/Linux desktop (not ChromeOS or Android) is crazy. That's not what this does, and they don't care about supporting us.
So far, Google's binary DRM blob isn't just restricted to ChromeOS either; it only runs on official Chromebooks running the official Google-provided image that haven't been rooted.
AFAIK it doesn't care if your Chromebook is rooted. My Glacier Snow Chromebook is "rooted" and Netflix (the reason we bought it) continues to work well on it.
ChromeOS runs on a Linux kernel, but the entire experience is very different from what you would normally expect from a Linux distro. I call the more recognizable distros "GNU/Linux" to differentiate.
Also, the codec used is actually part of the proprietary blob, and there are no requirements as to which codecs or containers a particular DRM scheme supports, so in theory every DRM scheme could require a different, incompatible proprietary codec and they'd still all be 100% standards compliant.