As of now, I don't think there exists a solution of that problem in eZ Publish. I guess what you're after is a system similar to links in the linux OS (where new node locations include the child structures), this is a dream/request of many eZ Publish users.
Two ways of coping with that problem know to me are:
1) Copy subtrees (requires separate management from that moment on). 2) Create structure copies by manually creating node locations for each node. That's manageable from just one subtree, but the problem here is that you can only manage content (you cannot modify one subtree structure expecting that it would change anything in other ones).
Looks interesting, but as far as I understand, this is just a functional enhancement when dealing with the subtree arrangement, the basic node functionality remains the same. So it seems to fall with scenario #2 in my list above. Nice submission, though.