Basically... changes should be made on the kernel, not on the distro? As in, installing packages aren't the optimal way even if the package manager itself can implement and configure said package on the kernel?
And since you mentioned being on a very tight budget... mind if I suggest hosting (only) minmal armbian images while leaving everything else to be configured and downloaded post-installation? Pretty sure that'd make the budget more doable to deal with, considering theres over 100 images available and the difference between a minimal and a pre-configured image being almost 3 GiB? (Imagine a cli user-friendly menu appearing post-installation, asking the user to choose between several window manager options to be downloaded and installed.). I'm aware armbian has a "not be on the user's way" rule but since this is a urgent matter...
Or even a "last resort android image burner" of sorts, that downloads an appropriate android image for the sbc "on the fly" and then burns it on disk/external disk/anything? (Since apparently android images "just work").
That aside, I appreciate the trust and transparency, but I'm not a linux pro let alone a dev by any means.
...even if I -do- enjoy treating my sbc as a "lab rat" of sorts, trying to figure out ways of making it work.
If anything, installing libgl1-mesa-dri (via bookworm-backports) makes the sbc fine for daily browsing needs and the eventual, casual linux native gaming -- the "miracle" you mentioned is already happening per se.