I'm pretty sure there's nothing in the code that checks for an existing node's status. If the remote node is published (which it probably should be, but that's up to the view settings), then the replacement node gets published again.

This does not seem like the right thing to do.