Granted, this won't be for every flavor of Linux, just the one I happen to be using. I imagine there's all kinds of different issues with the proliferation of Window Managers and graphics servers. Users looking for "just works" are not looking to dive into the various overlapping software processes.
Worse, the UIs themselves don't give you insight into what underlying settings you're manipulating when you click some button or toggle in the GUI settings. As a Linux user you know there's a conf file somewhere. But the UI obscures that from you. Perhaps the doc (or the source code (!)) says what the UI is doing. I'd love for there to be a little fly-over in the UI or even a path to the underlying configuration files. I'd be perfectly happy tweaking those in Emacs or Vim but I'm less happy hunting them down to figure out what they are.
I'm determined to avoid Windows, and I want x86 hardware because I can load it up for AI workloads. So I'm happy to be on Linux, but it comes with an overhead that most consumer level equipment doesn't. Linux is the equivalent of those shop tools that aren't safe by default, and are intended to provide the flexibility needed by machinists that know what they're doing. I'll accept that trade-off, but I'm not going to sell it to anyone who is a developer.
It's doable, but it doesn't "just work".
But yes; Nvidia has been the sore thumb of Wayland and Linux adoption for almost a decade now. It's interesting to see the tides finally start turning!
Funnily enough, it totally depends on the hardware. If your audio hardware is supported by Core Audio on Mac, chances are it will also work on Linux without problems. If your audio hardware is older, chances are it will not work on Windows due to the lack of modern drivers but will work on Linux without problems. This also applies to a lot of other older hardware like scanners/printers/... or even built-in peripherals in older laptops.
But if it's something strange (e.g., MOTU MIDI interfaces come to mind which use a non-standard USB protocol), you'll have to hack your own kernel driver which you probably don't want to do. Of course if you are adventurous and do hack your own kernel driver, even this will work, and you'll probably even find someone else's driver code on github.
What's also interesting about hardware support on Linux is that a lot of things which require extra drivers on Windows just work out of the box on Linux, especially if it's in any way relevant for servers like various network cards or if it's one of the many "standard" USB UART chips.