Presumably Apple is working harder on fixing all of those things than Microsoft, but maybe issues like that are why we still haven't seen an ARM MacBook yet.
[1] https://www.theverge.com/2019/11/5/20948092/microsoft-surfac...
Apple killing off 32-bit app support (and Carbon, QuickTime API, etc) is probably them preparing for an ARM transition. Any app that managed to make that transition is well-prepared for a pretty trivial "just change the compile target and press the button" ARM port.
Apple would be betting on Mac app devs quickly getting ARM ports of their apps out there. In the Microsoft ecosystem there's zero chance of that happening, so they have to rely much more heavily on emulation.
There's also a chance Apple could do some kind of bitcode magic[0], but they don't enable bitcode on the Mac App Store yet, so that is probably not in the cards [0] https://www.highcaffeinecontent.com/blog/20190518-Translatin...