I do, and as long as you leave them in the same place in the user share, they will run from either location without moving if you want. I use this to keep seldom used or low demand VM's from taking up precious SSD space and writes.
/mnt/disk1/domains/VM1/vdisk1.img can be moved to /mnt/cache/domains/VM1/vdisk1.img and it stays available at /mnt/user/domains/VM1/vdisk1.img
You must set the domains share to be cache no or only so the mover won't interfere. If you set cache no, then new VM's saved to /mnt/user/domains will be created on /mnt/disk1/domains, or whichever array disk is a valid location based on the other share settings. If you set cache only, new VM's will be created on /mnt/cache/domains
You can freely move them to array or cache locations in the domains folders and they will appear in /mnt/user/domains
If you don't understand how or why this works, don't experiment until you do understand, as there is a risk of irretrievable data loss if you mix /mnt/user and /mnt/diskX /mnt/cache paths in file moves, as the same file appears in both paths but the OS doesn't know it's the same file and can overwrite it with itself, resulting in a zero byte file.
If you stay out of /mnt/user completely for file moves you are safe.