So far as I understand it when in the same pool cross-subvolume COW should be valid (as shown in /data on the server) - even if technically under separate mounts.
I haven't yet found anything newer than this:
The clone can be in different subvolumes but the source and destination must be the same mount point.
There's a similar effect with btrfs send that might be related, and it has patches upstream.