Photoshop falls into this bucket. It's on the C++ side and does "some funky things" in the way of SIMD to eke out more performance. If memory serves, it took them about eighteen months to get an Intel native version out the door after the PPC/Intel transition started.
Any serious audio apps are going to have an equally hard time, they do a lot of hardware tricks in order to lower latency, and since they're not mainstream apps like MS Office or Adobe CS, they have much smaller teams of developers. That whole industry is very slow moving.
Finally you've got CAD and 3D stuff. Obviously that requires good drivers. In fact, that's another way in which Microsoft will have a much harder time with this transition. Apple only has to write a driver for the one audio device that's in every Mac, the one GPU, etc.
I wonder how much of that codebase is shared between Windows and macOS though. It's quite possible that Microsoft could take advantage of a lot of porting work that has already been done for Apple's M processors. If you support Windows/x86 and macOS/arm then it's probably not much more work to create a Windows/arm port. Unless there are compatibility issues with the Win32 APIs themselves?
In my C/C++ experience - it’s a big push that a software company would just rather not make. Even if you already have an ARM SKU for a different OS, all sorts of things can cause trouble. If you’re coding in C/C++, you’re probably pretty interested in performance and you’ll have a lot of hand tuned assembly and/or SIMD operations, and that can be a big pain to port, especially with different compilers and intrinsics.
I can only imagine the conversations that go on at Adobe or Autodesk or others when debating new platforms and SKUs. Given that even Microsoft wasn’t committed enough to ARM Windows to make a x64 emulator for it probably worked against this.
Honestly how hard is it to port software to ARM?
Electron apps just work, .NET just works and Java does too. So does every language that isn't C/C++. And even on the C/C++ side, unless you are doing some funky things I doubt it's more effort than adding a release configuration that targets ARM in the build pipeline.