I was talking about boot.iso installations not Live.
For the Live image your target environment is the same as the installation environment. Trying to optimize the installation environment to use less resources doesn’t help here, because if you don’t have enough resources to run a DE and a browser on the target environment, there is no point installing it.
The boot.iso is used to install a custom system on a custom target, and here it becomes critical when installer uses more resources than the workload which it is supposed to install.
This does happen currently. I may want to run nothing but a static web page on my tiny home lab server, but I have to run entire desktop environment and dnf to get that homelab setup. And here remote web installation can help, because it removes that overhead. The dnf part still will be a problem in that case, but it can be improved with bootc.
You do need to put some effort in your arguments.