hope this helps with the dumbster fire of the virtualbox version in the official Ubuntu repositories
(virtual box basically “breaks” on Ubuntu LTS once a newer HWE kernel gets released unless you install a newer version of it, leading to hundreds of support threads every time this happens)

If we are talking Silverblue then podman is your pick for everything Flatpack “can’t”
there is no big push for cli flatpack since this already a solved cause with containers for podman/docker/kubernetes

however no matter how you approach this you will always have dependency security issues
unless you built every flatpack/container yourself you are at the whim of the creator of it to keep every dependecy updated
this is already a known vulnerability factor in the container sphere on topbl of the threat of 0-day exploits

chances are you already used the external nvidia kernel module prior
the dkms package is just the “catch all” way which works on most setups
(at least on Arch Linux)

it doesn’t matter if you use paru, yay or heck makepkg if you are compiling packages with hilariously large sources like for example webbrowser (librewolf, brave, ungoogled-chromium, firedragon take each like ~30 GB) without pruning the build cache afterwards

afaik linux and windows shows different GPU memory clock speeds but it’s basically the same (1:2 conversion)
most likely because bigger number = better?

my AMD 6000 cards does the same

typically it’s based on the last kernel release of the year which gets promoted to LTS, not because of certain features

if you just need software to set up virtual machines you might look into Gnome Boxes or virt-manager which don’t require external kernel modules like Virtuap Box to work

anyway these issues typically happen on Ubuntu based distros (like Linux Mint) because your linux kernel is to new for the Virtual Box version (or the Virtual Box version is simply too old)

for someones who values security above everything else thats totally fine
but for someone who wants to reduce e-waste by prolonging the life of a phone with at least some updates this might be not the best solution

CalyxOS supports Pixel devices far longer than GrapheneOS does (they drop them once Google drops support too)