Close, but not exactly. [ @mrz put the kibosh to my feature request for CLI/API to quickset: Is QuickSet available via the API? - so this be one solution for a better QuickSet 
]
It's /container actually where I run into these "user input" needs. Today I use a script per container that manage a particular container. But it's hard to be generic, so the script requires a bunch of variable in the code â that might need to be changed for a particular router â and editing a script isn't very "user friendly". For example, if you look at my serial2http container, you can see how complex installation is to describe. A few user prompts to install avoid a lot of writing: GitHub - tikoci/serial2http: RouterOS container that proxies serial port via HTTP using TCP serial (RFC-2217)
For example, what a container's root-dir should be is not that easy to abstract/guess, so be good to get a user to "confirm" the path. And if you think each question in $INQUIRE's array is mapped to each on of a container's environment variables, to confirm or alter how the container runs, the logic here might make more sense.