If the original package is dead, you might be able to convince the AUR maintainer to switch to the fork.
In other cases, maybe a package with
<main feature>
added in the name could be created. I'd posit Supersonic as an example, where alternative packages exist just for enabling Wayland. It's still the same upstream, but an additional option in the build is required to enable Wayland.
Similarly, Emacs offers multiple versions with different build flags, though in this case it is using the same PKGBUILD for all versions.
If you have your own music collection, I can really recommend normalising everything to a LUFS value of your choosing. (A common value is -14 LUFS for most streaming services Source)
Note there are two types of normalising, dynamic and linear. Linear is what you want as it'll only move the average loudness to your target, preserving the difference between the quietest and loudest parts. Dynamic normalization squashes the quietest and loudest parts into a narrower range.
From my testing of the Wayland backend when it was still hidden behind a registry setting, it's mainly for DPI awareness. For example, I use a 1440p screen with 1.25 scaling. Currently Wine through Xorg therefor sees my desktop as 1152p high. With the Wayland driver it would still correctly identify as using a 1440p screen.
Did you set the correct block size for your disk? Especially modern SSDs like to pretend they have 512B sectors for some compatibility reason, while the hardware can only do 4k sectors. Make sure to set ashift=12.
Proxmox also uses a very small volblocksize by default. This mostly applies to RAIDz, but try using a higher value like 64k. (Default on Proxmox is 8k or 16k on newer versions)
In not sure what difference it makes. AMD already supports VAAPI for accelerated video encoding/decoding.