If you’re installing an HBA at home, it’s better to immediately install something like a Noctua NF-A4x10 on it. You should also immediately check the type of hardware initialization. If the system boots into EFI and the HBA is old and only supports BIOS, there may be problems. Otherwise, everything works perfectly with almost every device.
Because of the Wayland architecture, you simply cannot do it differently. Because Wayland is not a window manager, but a subsystem for working directly with video. This is not a new X11 server, it’s a different architecture. Therefore, by default, no matter where you choose, the render will be output to tty0 of your main server. You have only 2 options - use Wolf as is or manually assemble https://github.com/games-on-whales/gst-wayland-display and limit it to one video card via systemd. gst-wayland-display literally forcibly transfers the render not to tty0, but immediately to the stream for Moonlight.
So it’s not that Wolf is too complicated, it’s just that what you want is a rather complicated case.
UPD: although it is possible that you will be able to do this using wlheadless-run, but this will most likely be worse in terms of performance compared to gst-wayland-display. Although for a simple KDE session, I think there is no difference.
UPD2: I checked and, as I thought, regular applications will get along fine if you run them through wlheadless-run, but everything that requires vulkan may break. it’s the same with video cards. Simply specifying primary will not guarantee the use of a fixed card. But just for office work, I think it will be fine. however, as soon as the case starts to go beyond the standard, everything will start to break down if you have more than one GPU.
Просто используйте wolf: https://games-on-whales.github.io/wolf/stable/user/quickstart.html . Всё уже готово из коробки. Правда для KDE сессии придётся пересобрать KDE в контейнере вместо wolf-ui .
SNAP in the recommended packages of the ubuntu-server metapackage. Ubuntu installs all recommended packages by default. So SNAP is in the server installation, moreover, it can’t even be simply removed without completely blocking in apt policy.
If you’re planning to use old hardware for hosting, don’t use Ubuntu. SNAP will kill performance.
So your choice is Debian.
P.S. VPS is already a Virtual Private Server and you can’t install ProxMox or any virtualization on it. If you want experiments, look into containers.
I think the problem has been slightly exaggerated. If you’re not hosting several dozen services, you can reduce your attack surface down to one Nginx server. For an even stricter setup, just enable mTLS.
Install a clean Arch, then install Podman and run the wolf container. You will have everything needed in the containers. If you wish to play directly in your browser, run the moonlight-web container next to the wolf.