You seemed to be implying that this was some unique problem with OSX and that's what is holding you back from trying M1. But really, it sounds like what is holding you back is just the normal barriers of changing platforms.
Personally as a Windows user I am hoping that Windows for ARM gets supported on M1 soon, but I don't think it's so unreasonable we're not there yet, and I am not going to discount the whole platform just because of it.
What is holding me back from trying the M1, personally, is cost. I just paid $950 for a Ryzen 7 4800H with 16GB and GTX 1660 Ti. It can't hold a candle to an M1 Macbook in battery life, but I know I can run my programs and play my games and not think twice about it. My failsafe is an electrical outlet. I'm hoping I can end up trying an M1 (or successor) through an employer though! I spent the past year using a ~2014 Macbook Pro through work, and for work things, it was better than my Windows machines for working on projects where everyone else used bash on a Mac. As WSL improved, I was able to be equally productive on my Windows machines and tend to use them and not bother with the Macbook Pro.
That's all a lot of extra anecdote you didn't need, but to be sure, I'm not trying to single out OSX - the OP singled it out by saying, essentially, "you're using it wrong!"