Good question. For updating apps it is not needed to restart ShinyProxy: if you update Docker images, Docker will run the latest ones. When updating app configurations or adding apps, it is currently required indeed to restart ShinyProxy.
If the behaviour you are after is supported by Spring Boot, we can support it for ShinyProxy too.
With the current behaviour, note that an admin user can see the live usage of ShinyProxy in the admin view, so you can know you are not bothering users (or which users exactly you are potentially bothering) when doing a restart.