Hi
That idea only really makes sense for one setup, in fact for Factory Setup 1. There are already several different setups with other arrangements, and running scripts can alter the setup drastically as well. In fact, the way the instrument is laid out is very very 'soft' - it can be remodelled in all sorts of ways.
I can see that a generic UI will be very hard to implement given the flexibility of the system and even if it could be implemented, it may not be on an abstraction level that would be of any help. But there is still the issue of those wanting to learn - not only play the Eigenharp but play music in general - and I think at least the Pico is directly aimed at those people. I'm one of them. I mor or less need some visual feedback.
A helpful UI for me may need to be based on / linked to user setups. It should show me the current setitngs (instrument, tonic, scale, ...) and the available settings (like available instruments, scales and so on) with the key mappings. If the UI also allows to change settings, even better.
I imagine a UI framework, where someone creating a user setup can create an according UI and changing setups will load the new UI. Maybe even allow multiple UIs one of them being the default (which also can be none / null). And yes, running scripts may break the UIs. But I would accept this.