It seems like the kind of thing you could "low code" in the sense that you write a schema and the settings UI is automatically generated.

I don't know what you're programming in but you should have some table in your app that has

  * the name of the setting
  * the type of user interface control to use
  * how to get the settings data out of the app and format it for the UI control
  * how to set the settings data out of the UI control and apply it the system
  * other metadata to set the order, put the setting on the right screen,
    make them searchable, whatever

It is possible that the getters and setters are closures, or object references, method references, or a path of some kind (like the name of something in an .ini file or "property1.subproperty5") depending on the facilities used in your language. It's not crazy to keep settings in something like a sqlite database. Similarly the UI control could be specified by name or you could have a function that creates it.