Widevine is only one of several implementations of a Content Decryption Module; it just so happens to be by far the easiest to license (though that doesn't mean that's easy!).
Noope. Netflix has explicitly stated, at W3C, that they absolutely won't use any open EME implementation.
In practice any open CDM that you implement yourself will be totally useless. The "open" parts of EME have no real utility, and exist only to be able derail criticism by making rhetorical arguments about hypothetical open implementation, even though it's by definition exactly the opposite what Netflix and Google designed EME for.
But EME includes a fully freely implementable Clearkey spec. Ultimately sites generally don't want to generate keys for it, but it can be done.
2. To create market barriers for anyone who wants to compete with existing streaming services like Netflix, Spotify, and Youtube Premium
3. To create market barriers for anyone who wants to compete with Chrome, Safari and Firefox
4. To replace old proprietary plug-ins from Adobe and Microsoft with new proprietary plug-ins from Google et al.
To be fair, you can make a similar argument about what's the point of a standard for the video element: in reality, you need to support H.264 encoded video, so just supporting Ogg/Theora/Vorbis (as some early implementations did) doesn't suffice, so what's the point of that standard? (Also the img element, the object element, etc.)
But yes, EME is different because it fails to fulfil its use-cases in a fully free implementation (one can imagine, potentially in the future, a free software implementation that passes encrypted content to a hardware module that implements the decoding, but that seems like little gain and unlikely to happen).
https://www.w3.org/TR/2017/REC-encrypted-media-20170918/