I have been a Linux user off and on over the course of a decade, in my personal experience - now is the best time to jump in.
The only caveats immediately I can think of:
- Anti-cheats don't work (sometimes games turn on linux-only toggles - however it is NOT default, the developer has to opt-in to these settings)
- Some streaming sites - chances are use Widevine DRM to control playback - such as Netflix, Hulu, etc have issues without special configuration to the browser (use the Flatpak version of a browser to have the best experience). Hulu in particular needs location services - which only works reliably in Flatpak versions provided by Mozilla, Google, etc - which also package Widevine.
- Wine isn't a silver bullet - you will encounter software issues using it. Music production, for example can work - but your plugins (VSTs) might not. Chances of them working are even lower (if not 0) if you use anything that relies on iLok - heard it's common for Native Instruments plugins to have that bundled.
Look at winedb and the gaming equivalent protondb for guidance. Some comments reply with configurations that might be necessary - typically command line arguments or winetricks configurations. Some games have very devoted communities - like Roblox - which make software to natively run the x86 Android client with special sauce to support Roblox's anti-cheat (the VinegarHQ's project Sober) - but not every community has people this devoted. Your mileage may vary.
Outside those things, for the most part - the software you list does work on Linux natively.
For a beginner distro - especially if nVidia support is required - use
bazzite. It works slightly different than a traditional distro, primarily cause it's an atomic distro. I use this personally with an RTX 2080 Super - works flawlessly.
Atomic distros require you to reboot to apply changes such as updates and software installs - but, only if you install software outside of Brew or Flatpak - in bazzite, it is installing software using the rpm-ostree install command.
However, most software can be installed without that command - and, most software can be found in Brew and Flatpak anyways.
If you want more of the traditional experience, use Fedora - use whatever desktop environment that speaks to you. Fedora calls these "spins" - there's a KDE spin, XFCE spin, etc - choose whatever you want.
Best experience is still using AMD and Intel cards (e.g. for 100% Wayland support) - as both of those have open-source firmware. nVidia is playing catch up, and only recently (within the last year) distros started shipping their open-source drivers on Linux. Years and years of work is still needed for this to actually mean something, though - as like mentioned, the Wayland project focused more on cards with open source drivers instead and maximized compatibility with them, as it was easier for them to support than nVidia cards. Wayland is stable despite this - but along the way I have encountered issues with sleep/wake, so turning off sleep on your system is probably best for stability on nVidia systems, and just leave it so the monitor turns off. Turn your system off to properly save power. 2030 is looking bright - provided nVidia still exists as at all as a consumer company by then. Their presence in this area is already seriously lacking.
Back when I started using Linux in 2010/11 - Ubuntu by Canonical was the name of the game. Outside of the corporate associations they've made throughout the years and the Unity interface and it's complaints (they use GNOME now) - Ubuntu now is a completely different distro, but Canonical have a tendency to introduce issues in "stable" versions that are only fit for an alpha release.
Snap, outside of the complaints levied against it - is a nightmare to deal with. Canonical insists on packaging as much of the system inside it, with zero regard for how it interacts with the apt package manager (made by the amazing Debian project - which is the distro Ubuntu uses as a base).
For example, I was able to brick a fresh install after simply installing updates - which is normal to do on a fresh install, as the packages will probably be out of date on the image you downloaded by the time you install it. After doing that, apt lets you know if packages are no longer needed (a feature built in and quite useful, actually). The problem is, every package installed in Snap is dependent on Snap itself, which is not the issue here ironically - it makes sense (this is the same for Flatpak). No, the issue is if you run the command to auto remove packages that apt says are no longer necessary - on Ubuntu, that means nuking the desktop environment and tons of other critical system components.... on the desktop version of their distro, shipped for desktop usage. Yeah, on Ubuntu - removing non-needed packages is actually a dangerous operation that can trash your install.
This was in 2021/22 - I have never touched Ubuntu after that, and don't plan on it, either. I don't run it on servers, either. Nothing.
Ubuntu, pre-Snap - was actually a good distro. But I could never recommend it to beginners ever cause of how impressively easy it is to brick an install by simply using it. You need to be super careful when using it, otherwise you will destroy your install and have to re-install - which at that point, like me, you might as well distro hop again.