Ditto on having services expressed in more portable/cross distro containers. With NixOS in particular, I've found the best of both worlds by using podman quadlets via this flake in particular https://github.com/SEIAROTg/quadlet-nix
I too was experiencing odd/erratic pairing issues with DualSense controllers and this RTL8671B based dongle, and using the older firmware entirely fixed it. Now four controllers can be connected simultaneously without issue.
I've wondered if that's to make dealing with full disk backup/forensic collections/retention legal hold/etc easier: keep the official amount of end-user device storage to a minimum. And/or it forces the endpoint to depend on network/cloud storage, giving better business intelligence on what data is "hot".
Pinning to the physically closest core is a bit misleading. Take a look at output from something like `lstopo` [https://www.open-mpi.org/projects/hwloc/], where you can filter pids across the NUMA topology and trace which components are routed into which nodes. Pin the network based workloads into the corresponding NUMA node and isolate processes from hitting the IRQ that drives the NIC.
There is at lease one open issue¹ with the clipboard crate that causes a high amount of wakeups (under Wayland at least). Whatmore, the wakeups scale with the number of terminals open. The project is ruthless about performance[latency] regressions, but not so much about performance[energy] overhead.