Any way to add mapping to current instance to prevent un-graceful rebooting?

I run multiple servers for a small group of 10-20 friends. A couple users like to hop across modpacks.
I am frequently asked to spin up a new server (a very quick task, usually), but adding the new container to the mc-router via updating the mapping command in `docker-compose.yml`, then running `docker-compose up -d` (expectedly) causes all users connected to any server behind the proxy to be disconnected.

Is there any way to add a mapping to a running mc-router container without shutting it down and restarting it?

Start with the mapping command and container lifecycle described in docker-compose.yml, including what happens when docker-compose up -d is run. Determine how a running mc-router could accept a new mapping without disconnecting existing users; done means adding a mapping preserves current connections and routes new connections correctly.

Written by the indexing model from the issue text.