Really I think a temporary dual boot to test everything would be the sanest option, and then when you're ready to commit, back up your home folder and repartition your drive accordingly. If you end up never ready to commit, well, second-gen Ryzen is officially supported on Windows 11 as long as you enable fTPM and Secure Boot in your BIOS.
Here's a few pointers based on what I've found out:
The desktop environment or WM is important. Given your need for Steam Link to work I'd suggest using one with X11, as last I checked Steam Link just gives you a black screen and audio under Wayland. Linux Mint would carry over your knowledge of apt while maintaining an interface that's pretty familiar to Windows users and is I believe still an X11 distro for now.
I got the EA app working using Bottles but it constantly feels like a cat-and-mouse game fixing it whenever it has an update. I basically stopped using it altogether for that reason. Not trying to scare you off — it's just not a great experience.
Play with drivers for your GPU. The situation with Nvidia is, I'm told, not as dire as it once was on Linux but still needs more work than AMD or Intel graphics to work well. The proprietary driver may still give the best experience on games, though Nouveau seems to be doing very well. This is admittedly something I need to come back to in order to confirm (I have one machine with Nvidia graphics and it's in storage specifically because Nvidia graphics under Linux were such a pain).
It'll be compatible with 5 Gbps devices, but if you're intentionally looking to restrict even 10 Gbps devices down to 5 Gbps for some reason, you might be able to find something in your BIOS that lets you do that, or you can get a USB 3.0 extension cable that'll limit your speeds to 5 Gbps.
I moved to Pop!_OS entirely when I built my new system earlier this year (had already been using it on my non-gaming laptop for several years) and relegated Windows to an external SSD that has been essentially collecting dust — I think I've used it three or four times.
My experience isn't the same as everyone's, but I'm not in love with most multiplayer games, my work uses software that can be run within Wine/Bottles or a browser, and my preferred creative outlet is writing, which could also be done in a browser if I wasn't such a picky bitch (I am, but Scrivener barely needs massaging to work under Wine and can even be made to look native thanks to using Qt).
I would argue that NixOS absolutely is the OS you get if your time is worthless, but not every distro is the same. I'd argue that if you need something that doesn't have so many issues a stabler or easier to use distro (Debian, Ubuntu, Pop!_OS, Linux Mint, and even Fedora or openSUSE) is going to be a better option than trying to bend specifically NixOS to do what you want.
I personally use a mix of Pop, Debian, and Fedora, not because they're particularly powerful, but because they tend to be more straightforward for what I want to do than NixOS, Gentoo, or Arch. I don't mind tinkering, but for my main machines I don't want to tinker much.
Edit: I should clarify that there are plenty of reasonable uses of Windows and I don't fault anyone for using it especially if their familiarity is keeping them from understanding Linux as well as they want to. But I also would make the case that there are a lot of distros out there.
Ares as a project has a goal of accuracy at any cost, so tends to need a lot more resources than most other emulators. Before the tragic loss of Near, they wrote an absolutely exceptional article about the development of bsnes/higan and how much power it required for cycle-accuracy of SNES hardware, and it's way more than you would think is feasibly necessary given that emulators like ZSNES (or Gens, as was my Sega emulator of choice at the time) ran under a crappy Celeron in the 90s.
I will say your CPU will likely throttle back well before it'll shut down due to overheating. It might affect emulation performance some, but your PC shouldn't shut down or anything.
This is my real problem with this (and also broadly pointing the finger to the "Unix philosophy" whenever a project like systemd or Wayland exists, ignoring that the large, complex, multifaceted, and monolithic Linux kernel itself flies in the face of that philosophy). Linux may have originally been built to be Unix-like but has become its own thing that shares a few similarities with Unix.
…Except Debian wasn't even user-friendly when I used it two years after Ubuntu's release. Red Hat Linux (not RHEL, which came later) was the only distro I'm aware of before Ubuntu that was more UX-focused.
Edit: I forgot about a few others — SUSE, Corel Linux, Lindows/Linspire, and others. Buuuuuuut most of those distros don't exist anymore. I still stand by that Debian didn't used to be as noob-friendly as it is these days.
Oh hey, I was thinking about DSL recently and was bummed that it'd been discontinued for so long. It was my first Linux distro, downloaded over the course of I think a day and a half over rural dial-up. I moved to Ubuntu once I was able to get blazing fast 1.5 Mbps "broadband" but DSL still holds a special place in my heart. Going antiX-based was probably a good move to make it a bit more manageable, and while I downloaded it originally because it was 50MB I agree that it's probably more realistic that people will download it with a connection much faster than dial-up, and the hard cap on a CD-sized image is I think a good compromise. It's still, as the name says, damn small, at least by modern OS standards.
Really I think a temporary dual boot to test everything would be the sanest option, and then when you're ready to commit, back up your home folder and repartition your drive accordingly. If you end up never ready to commit, well, second-gen Ryzen is officially supported on Windows 11 as long as you enable fTPM and Secure Boot in your BIOS.
Here's a few pointers based on what I've found out: