It's a common practice to offer HTTPS, but you shouldn't think of it as dogma. It's perfectly reasonable to provide both so that people using old terminals (an iPad v1, or an old game console for example) can access the content without technical issues. Or if you want a very low-resources device to access it.
It's all trade-offs and use-cases. One is not a superset of the other.
It's like saying every door should have a lock. No, not every door is improved by adding a lock. Many use-cases are actually not possible with a lock.
Different situations have different tradeoffs, and different people value different things.
There are many valid use cases for HTTP, and more broadly, keeping old devices and experiences working as time passes
My country (France) has many buildings and bridges from 500 years ago for instance. I hope these get preserved as there is a lot to learn from them, lots of beauty in them, and they may be more and more relevant in the future.
Not everything should disappear the instant there an alternative. Things co-existing is great.
As I highlighted above, a redirect from http to https is going exactly against this. If you care about MITM attacks for your visitors to that extent, you should not serve any traffic on HTTP. Yet that's a usability nightmare because of how web clients (not just browsers) operate today.
Browsers are finally starting to default to HTTPS without using a whitelist when no protocol is specified. That's the only reasonable approach, and hopefully in a few years, that's prevalent. Maybe browsers can also start doing something "smart" where they also fetch https resource when http is requested, and switch to https if they largely match.
Combining it with secure DNS is the only way to true protection against eavesdropping and MITM attacks.