Most video games already use UDP
For the hobbyist world, this option as a low level transport is not so bad imo. Like as a replacement for ENet which does not have IPv6 support today seems reasonable.
The main difference from an API pointer of view is that there is an additional multiplexing layer. On TCP/IP the byte stream is directly on the connection. On QUIC a connection can contain multiple streams - which are openable by both sides. And each of those streams is a bidirectional or unidirectional byte streams.
QUIC doesn't care what protocol you run on top of those streams. HTTP/3 is just the only one which is specified at the moment.
Many people here seem to not realize that TCP is used for much more then just http/https.
Quick might be nice for web traffic, but i see little reason to use it as an underlay for BGP for instance.
In terms of BGP and quic as a transport.
As far as i know, quic is not backwards compatible with TCP, and having two different transport protocols for the routing protocols that ties the internet together would be problematic in terms of migration.
Im not entirely up to speed in terms of how quick would handle MSS size, but this could pose a problem in some situations.
Theoretically? Depends on the transport and it's characteristics. There could be a theoretical gain to using something else.
Firewalls that dig deep into tcp packets sound like troublesome middleware with which good actors are in an arms, not something to go out of the way to support.
I'll have to look into potential MSS issues.