Vfs cache utilize hard link

When moving a file to a vfs cache full supported mount, rclone writes the whole file/folder to the cache directory which takes time and uses twice as much storage. Is there any reason why it couldn’t use a hard link?

For example
/home/user/downloads/archive.tar.gz
mv /home/user/downloads/archive.tar.gz /home/user/mnt/gdrive
mv operation takes a long time while rclone writes the file to /home/user/cache

rclone mount gdrive:data/user /home/user/mnt/gdrive --cache-dir /home/user/cache --vfs-cache-mode full --vfs-cache-max-size 250G --vfs-cache-max-age 24h --use-mmap --bwlimit 25M -v --progress

You are writing to the fuse mount though and the cache operation is happening underneath the covers so you can't easily hard link it.

It would most like require some unique refactoring to make something like that viable and would be cumbersome / not a long of "bang for the buck" for the one off type situations like that.

I do the same thing and just have double data for a bit while my uploads happen.