HTTP1.1 has a fundamental flaw related to request smuggling. Fixing specific variants of that problem is a game of whack a mole, as issues arise most often from larger server composition, not individual parts. Fixing the protocol flaw requires a major version increment and a phase out of the old one. Today the hesitation to do that gives us a mitigation option, but in general an http downgrade is a bad thing.
There are also features on top of http2 that a downgrade may break: gRPC and Server Side Events for example. The later is compatible with HTTP1.1, but could fail due to connection limits, as multiplexing isn't only about speed. Some web apps may handle that so gracefully, it turns into a performance thing again, but others could halt and catch fire.