Doesn't matter what you call Wine (and they'd argue it isn't an emulator, Wine is an acronym meaning WINE Is Not an Emulator), it's another layer of abstraction that'll slow things down. Particularly since you are talking translating dissimilar system calls, and it is an implementation done by reverse engineering. Not the kind of thing calculated to be fast.
You'll also have to forgive me if I call BS on the "more solid" thing. That reads like someone who has looked up talking points for Linux from a decade ago. Here at work we run a mix of Windows and Linux systems, but at the core of most of it is two Windows Server 2012R2 systems running Hyper-V on which most of the rest of the systems run as virtual machines. Know how many times they've crashed in three years? Zero. That number doesn't surprise me, rather I expect it. I expect modern systems to have problems nearly never.
If you have a Windows system that is unstable, the problem is with the setup, not with Windows, and you might wish to work on diagnosing and fixing it. Because Linux isn't magic, you can have a Linux system that is a rickety POS real easy. Don't get me started on some of the hacked together setups in labs that like to crash if you so much as look at them funny.
If you like Linux, that's fine, but trying to run an advanced, complex piece of Windows software that interacts with lots of other pieces on it is rather silly. To me it would be the same as trying to run a complex POSIX program setup on Windows using cygwin. Ya you could do it, but it is a bad idea. Just run the OS for which the software was designed.