yeah, i guess that can work but i think that would impact realtime services that depend on ephemeral rendezvous routing.
better would be to bulid in this "please repeat" message into your subprotocol if you ask me. this is an example of a case where you harm one use case by handling another.