Presets can already be loaded via scripts.
Yes, and then you need to have them available. Meaning you have to enter whatever prefs program, set parameters and save to file all possible settings you may wish to have available.
Can you explain the need for more control from the command line?
Sure.
* different palette settings depending on what daylight there is, with darker settings at night - currently I do this by juggling preset files, I would prefer to send RGB values regarding the various pens directly.
* sounds prefs, audio bell - I wish to control at least the volume without having one setting file per possible volume setting.
* ASL prefs - depending on context, I want to control how ASL requesters sort files so I don't have to do it manually every time
* screenmode/overscan - I want to control certain screen properties.. width, height, depth.. in one go, without needing to keep dozens of preset files around
* serial - I wish to easily change properties like baud rate from CLI/ARexx, as AUX:, SER: etc. AFAIK do not have parameters for such.
(Yes, I know there are options, like using
http://aminet.net/package/util/libs/DigNet)
I've always liked the way AmigaOS handles prefs and I like the env/envarchive 'thing' which I think is rather elegant and efficient.
Me too.
Also, why would I want other software to be mucking around with my preferences? Any software mucking around with my preferences gets deleted!
I don't know where you get this from, I am talking about the user - me - being able to control the preferences of my computer from my preferred user interface. There is nothing that prevents programs from mucking with your preferences already.