Too many people don't realize that it's not an open ecosystem any more. The Web is no longer an open collection of a large number of HTTP/HTML clients and servers. It's a singular platform, produced by control a centralised consortium of a small number of entities (browser vendors (mostly Google), ad vendors (mostly Google), and a few very large for-profit sites (mostly Google)) and since it is their product alone, they dictate how it works and they don't have your interests in mind. You not liking this fact doesn't make it untrue. We're not heading towards this endpoint - we're already there.
You will either obey the rules of the product (as dictated by mostly-Google), or you will stop using the product. It's no different in kind from either obeying the new Play Store policies or getting removed from the Play Store. It's no different in kind from either obeying the new Twitter terms or getting banned from Twitter. These are applications, centrally controlled platforms, not ecosystems.
If the Web decides that you need to meet some requirement but your corporate process is set up in a way that makes it onerous to meet, then you either change your corporate process or you get off the Web.
At least it still doesn't cost actual money or ID documents to be on the Web, like it does on the Play Store. I'm not very sympathetic to corporations who put roadblocks in front of themselves and then play the victim. The Web has demanded that you must have a streamlined fully automated process for certificate issuance and deployment, but, key point, this isn't an unreasonable requirement.
It's justified to keep a close eye on the rollout of new Web requirements, because unreasonable ones are surely not far behind. Google has just announced that in the next version of Android you won't be able to sideload apps that Google hasn't approved. It'd be folly to assume they aren't trying to impose something similar on the Web as well. But this isn't that, and can't become that.