I'm not seeing why this can not simply use the existing settings trait (and therefore be database backed), would you care to elaborate?

I didn't think about where to store the settings, but still I like to have the settings/configuration input validation code in some place (and not in the controller). This way the controller can be simple and when we need to add more settings we have a separate place to do this without messing with controllers and model classes.