Yeah, had that thought as well at some point. It definitely feels like
some constraint is slowly applied to the web, though I find the exact security properties somewhat nebulous. The one concrete requirement that seems to be pushed by this is that any host that expects to be accessed through a browser
has to be connected to the internet at some point - and
has to have an internet-registered domain name. (And at least the root of that name will be publicly visible in a CT log and will be processed and stored by who-knows-what)
Though weirdly, it doesn't even matter to which particular service the host connects or if the domain name actually resolves to anything.
But it does feel like some creeping "platformization" is going on: The requirements make it reliably a pain to run anything that's not connected to the internet, such as LAN-only websites or local web interfaces of IoT devices.
I wonder if the end goal is some sort of "app-storization" of the web, where some entity has the power to ban a site globally, even if registrar, server and users are all in a different country and even if the site only exists internally on some LAN. But then again, I'm unsure if browsers couldn't effectively do that already today - so if they could, why all the effort?
Taking off the conspiracy hat, maybe the tighter update requirements could be a push so that people finally develop some protocol how to securely update certificates on IoT devices. That would at least disprove the conspiracy theory.