HTTPS may not be proprietary, but it comes with many of the same drawbacks: central control, lack of transparency, more difficult to debug, and less accessible in many circumstances.

> central control

What central control? Your browser uses a trust store and there are multiple independent (but collaborating) groups that decide what CA:s to trust.

The rest of your supposed drawbacks seem like they would be the same in any system with encryption, right?

You rely on one of several central authorities to grant a user access to your website (or be faced with a scary message about your site being insecure).

Just because you can choose from one of several central authorities doesn't change the fact that you are reliant on them to authorize the user's ability to establish a network connection with you.

That means it is more like federated control IMO.

Whatever you want to call it, it creates extra complexity, failure modes, and barriers to information access.

True, Google's attempts at pushing SPDY and QUIC came later...

Those are not proprietary and have multiple independent implementations and are supported by all major servers and clients.