* a) whonixadvsetup directly apply/remove settings for the user.
* b) whonixadvsetup run a (bash) script that applies/removes the settings for the user. This has the advantage, that the code for setting/unsetting the setting can be shared between whonixsetup and whonix-setup-wizard and that it would also be possible to manually run it by the user or other scripts. Advanced users / custom builders could create a script that runs such settings scripts to customize their system for them.
* c) whonixsetup / whonix-setup-wizard could install a package, that applies these settings. For example, to add the necessarily settings for T142 it could install a `anon-ws-tunnel-t-tor` package. (It would be trivial for me to create such a settings package.) It would have the advantage, that custom builders could install such packages by default. I worry, that settings become too complex, that it would require too many packages for too many custom settings.
Applying a setting just means for example:
> Creating a file `/etc/uwt.d/40_uwt_disabled_by_script.conf` with the content `uwtwrapper_global="0"`.
Removing a setting just means for example:
> Delete `/etc/uwt.d/40_uwt_disabled_by_script.conf`.