The game being inherently multiplayer, this component is critical to the success of server operations.
However, the current optimistic implementation of the queue system can quickly be overloaded with tens of players attempt to join at the same time, as it was recently experienced on an intensive 100 limit server with a queue sometimes also containing as much players.
However, since the mods are loaded after an instance of the NetworkManager is created, this is no way to implement a different queue system and have server owners experiment with other ideas.
One such idea would have been to sequence players in the queue not only based on their priority (whitelist mechanism) but also based on a set time between each player allowed in: this would help flattening the data transfer spikes experienced on player join/download, avoiding to much of it at once, leading to server overload and/or network resources starvation.
There might be other problems related to too much players joining at once, but the core idea of this suggestion is to remove that burden for you, busy developers, and empower server owners with the ability to try things out, enhancing/fixing their instance.