For some config changes /reload command would be enough to apply the changes.
In that case marking the config with RestartRequired is overkill especially since that may cause a client restart.
It would be nice to have a ReloadRequired annotation to simply cause the server to call /reload and regenerate the runtime data.

Now, I do certainly see how some changes only require a reload to apply. Yet, the config screen is a client-side feature which will, in the majority of cases, not have any way of actually causing a reload on the server - how would you envision this working?

I feel like in most cases this can be covered by manually applying a tooltip to the affected options - do you see this differently?

Cheers