The problem with QUIC for these kinds of problems is that it is really multiple protocols stacked in a trenchcoat with no way to get at the individual layers.

The problem with QUIC for these kinds of problems is that it is really multiple protocols stacked in a trenchcoat with no way to get at the individual layers. QUIC has a connection setup protocol, a stream reconstruction protocol, a stream management protocol, a adaptive channel parameter discovery protocol, a resend protocol, a channel bandwidth distribution protocol, and probably a few more that I can not think of off the top of my head just for normal stream oriented transport. What you really want in this sort of use case is most things except adaptive channel parameter discovery (i.e. half of congestion control). You should already know the expected channel bandwidth and latency and can instead adapt in-context rather than using totally generic mechanisms designed under the assumption of a “uniform/static” network.