Is it okay to run off a writable 9pfs share when cache=loose?

I'm trying to run a virtual machine off of a writable 9p root filesystem. When the default caching mode is used, apt and some other tools fail; likely due to limitations with 9pfs itself. The error message produced by apt is:

Apt: Unable to determine file size for fd ... : No such file or directory

A quick search online suggested that I should set caching to loose when mounting the filesystem. Mounting the filesystem with cache=loose on my system did indeed allow me to use apt normally. However, now I am worried about filesystem consistency. [Kernel documentation](https://www.kernel.org/doc/Documentation/filesystems/9p.txt) states that this cache=loose is only meant for read-only systems and sadly doesn't elaborate further. So I present my question as follows: If I only access the filesystem through a single mount point where caching is set to loose, and I do not access the filesystem or its underlying directory otherwise, would I face any issues with consistency/coherency? Or stated in another way: Does loose caching effect the consistency of the filesystem when viewed exclusively from a single mountpoint? I'm using the following mount options: rw,trans=virtio,version=9p2000.L,cache=loose in my kernel command line and fstab.