It needs testing but I think -c option can work for this case, because the parent on both source and destination are identical, even if the new destination (the old source) has an unexpected received subvolume uuid.
At least for me, it worked once and I didn't explore it further. I also don't know if it'll set received uuid, such that subsequent send can use -p instead of -c. -c generally still confuses me... in particular multiple instances of -c -- Chris Murphy
