Support nondisruptive config updates?

GitLab Runner itself can reload config.toml on change, and apparently this works for "most" options (source). However when updating the ConfigMap given in a Runner.spec.config it doesn't have any effect, because where that's mounted into the runner pod isn't used directly, rather I see it goes through some kind of process and the result is copied into another location to be used by the runner.

Is there any way to force the config.toml to be reloaded without restarting the runner itself? If not: please consider this a feature request.

(Please let me know if there's a better place for me to ask this question, rather than raising an issue!)