The rationale is similar to ISPN-2939, the async marshalling option can cause inconsistencies because it can reorder commands.

But the case is stronger when the replication queue is in use, because the RpcManager.invokeRemotely() call already happens on a the replication queue's background thread. The user thread is already free to do its thing, so there isn't any reason to do the RPC on yet another background thread.