My 2¢: Pick a free time, make a small list of tasks that you do in Windows and spend time diving into what options exist for doing that in Linux (usually there will be multiple). The aim should not be to remember how to do it (less memory used 😁) but on figuring out menu structures, terminologies, etc. While going through your lists, you’ll end up familiarising yourself with (hopefully) gimp, the terminal, libreoffice, etc. You’ll hopefully also develop some tricks for searching for information on stackoverflow, GitHub, or in the various forums. That should help resist the urge to just switch over to Windows, and find a solution quickly.
It will take time. Sometimes, things will just not make sense - but finding solutions to problems is (probably) what is making you interested to begin with. Don’t look at it as a decision, more as a journey to start.
One particular pain for me in VSCode is that it puts a .vscode folder in my repo, which I have to specifically exclude from git every single time. I can’t expect other users of the repo to use vscode, let alone my settings synced to git. In firefox, it sometimes gets tricky finding the profile folder, as it changes across distros. Similarly, I always find it difficult searching for service files (there are at least 4 folders that I now know of). All of this searching around and doing little things used to be irritating - though you get used to it, and figure out shortcuts. TBH - windows has some of this too - I had to customise a bunch of stuff on first boot.
No clue about Nvidia - I hear they make something called GPUs but I have not been able to afford any, so can’t say I relate.