There’s some notion that browsers might support HTTP/2 for http:// URIs when it’s *not* the “general/open” Internet; it sounds like your use case might fall into this bucket.
I'd be more comfortable with MUST than might. Making http an
optional feature will guarantee that we are forced off of the
mainstream once version 1.1 dies, in perhaps 10 years, and will have
to use either open source or specially-crafted proprietary software
at that time. Much as I love Open Source, I'm not sure we should be
in the position of forcing people to use it.