Back when I did my setup,
there wasn't a clear guide on the matter though, and it was rather hard to setup.
If you're interested, I can link you all my bookmarks on the matter which I made back then though, however none of them were for Fedora / Nvidia specific.
For the pass-through mode,
I use VFIO (Virtual Function Input Output) with kernel / grub configurations, to always dedicate one of my 2 GPUs for the KVM (Kernel Virtual Machine).
You'd be looking for hot-plugging/hot-swapping your GPU instead, to un-attach your GPU from Linux and re-attach it to your Windows KVM when it boots.
Back when I was setting up my system, this was not possible on AMD yet due to a bug (Can't vouch for Nvidia or if the AMD bug is fixed by now though)
WASM = WebAssembly,
this has nothing to do with Java,
but with JS (JavaScript).
JS works with JIT (Just In Time) compilation, meaning every user that requests a web page, will request the JS and your browser will compile that JS on the fly as you request it.
WASM on the other hand is pre-compiled once, by the developer, when he/she is making the code. So when a user requests a WASM binary, they don't have to wait for JIT compilation, since it was already pre-compiled by the developer.
They only have to wait for a tiny piece of JS,
which is still JIT compiled,
a tiny piece of JS to load in the WASM binary.
This saves the user from waiting on JIT compilation and thus speeds up requesting web pages.
WASM also increases security,
since binaries are harder to reverse engineer then plain text JS.
Due to those reasons,
I believe WASM will be the future for Web development.
No clue why people are hating on WASM,
but I guess they just don't grasp all of the above yet.
I will not touch Bedrock edition,
especially not since it requires you to sign in on your Windows with a M$ account, while my Windows KVM is Ameliorated, which strips the ability to do so, nor would I want to if I could.
Flatpak:
To limit shady proprietary software from accessing your full storage / hardware.
You can manage the sandbox access through tools like FlatSeal.
Snap:
To ruin your day / user experience.
Both where introduced as a universal way to distribute packages on various distros.
Root on Android is a necessity for me.
I've been rooting all droids I use for the past 10 years or so.
Imagine using Linux as a power user,
without being able to use sudo/su.
Also, Magisk does not just allow any application to access root, you have to manually allow apps to make use of it.
Just like administrator rights on any other OS,
things only go wrong if you don't know what you're doing, and then grant rights to something malicious.
Gotta admit, it was very hard to setup initially.
However it's been working perfectly ever since I did.
Been using it for about a year or 2 now.
Also when I linked the Arch wiki,
I noticed in it's article that there's now a gpu-passthrough-manager,
which will likely make the process of setting up a little bit easier.
Amazing, basically native speeds,
currently playing Horizon Forbidden West with maxed out graphics and DRS disabled at a steady 60-80 FPS.
Previously I also played Horizon Zero Dawn in it, also maxed out graphics, steady locked 100 FPS,
below is a benchmark comparison of HZD in the Linux host OS and the Windows KVM guest OS:
And I configured my kernel to support VFIO (Virtual Function Input Output).
So I can fully pass through one of my GPUs to my Ameliorated Windows KVM,
which I use for both work and gaming.
No easy way to set it up I'm afraid.
But if you're interested,
I posted all the bookmarks I made, with tutorials and tools, when I set mine up here:
https://discuss.tchncs.de/comment/9245159