I don’t fully understand that question. It’s working stateless so there is no need to store any “current configuration”.
Install routines are “twin mode” capable: you (as a user) can run them in interactive mode, but we have put substantial efforts into recently that you can also run them in unattended mode.
That is what is used during unattended install as a big batch but you can also call them one by one.
In that case the routines take their input from /etc/openhabian.conf (which is just another bash input file that gets sourced on startup, effectively setting all parameters as env variables).
So if you want to you can use that as a config storage to store your web input to.
When you want to trigger a routine from the web, you can pass arguments by setting env variables.
On Linux support, what’s your point ? We support all debian systems, too. It’s running on x86.
There’s restrictions that not every function and 3rd party tool works on every system, but that is mostly
because of hardware related and other low level stuff like e.g. kernel modules.
It’s a lot of work to develop and mature code and to test against various HW and OS variants.
And it’s even a hell of a LOT more efforts that need to go into supporting users.
You must do that if you want them to keep using your tool. Please don’t underestimate that.
Have a benevolent look at the openHABian code please to find out if you can integrate it with your cockpit and let’s join forces.