Yes, a RAM File System volume can be shared over the network exactly like a local NTFS volume.
Share it the usual way (right-click the drive and choose "Sharing", or net share Queue=R:\) and other machines map \\server\Queue. Nothing special needs to be configured.
We tested this extensively with cross-machine byte-range locks and share modes correct, and oplocks/leases behaving exactly as NTFS does. Directory change notifications work too, so FileSystemWatcher fires normally. That's everything a file-based queue needs: atomic rename-into-place, or LockFileEx coordination between producers and consumers.
One thing to keep in mind: the contents live in RAM, so a volume is empty after a reboot by default. If the queue must survive reboots, create it backed by an image file and enable auto-save. It is then saved periodically and at shutdown, and re-mounted automatically at the next boot.