I probably made a similar point in another thread about software design. There is probably some devil in the detail, eg sometimes you might want to flip between scales, tonics & octaves that you have setup earlier, but not change loops, other times you might want a more complete change of setup. And I doubt either of these fit brilliantly with the way EigenD works now, or at least Im yet to see any indication from Eigenlabs that such things are in the pipeline or are trivial for them to implement.
Certainly I would be in heaven if I could just press a key to flip though instruments, scales, tonics & octaves I had set earlier, or hold down the mode key and press a key to recall such a preset. Alternatively if I could get the presses of certain keys out from EigenD via midi or OSC then I could take care of this sort of thing by hacking together software to do scale etc changes to the midi coming from playing the pico, eg by using max4live.
I do find it interesting to consider how practical such changes to behaviour are for Eigenlabs to implement, how wedded they will remain to the assumptions that were present before lots of people got their hands on a pico, whether all of these issues can be solved by tweaking how things work now or bolting on functionality as opposed to having a more radical rethink, how much I will be able to do via scripting, what will happen when the software is opensourced, etc. I think some of the issues are a bit tricky, some may be solved by the plan eigenlabs already has, and clearly they are keen to listen to users which is great, but I dont expect instant miracles, so I play the wait and see game.