Modeler and lighter, or workstation and laptop, on one project folder.
Put the project directory (.blend files, textures, references, linked libraries) in the shared folder. Textures and assets stream when Blender reads them, so opening a heavy scene from the other machine does not wait for a full copy. Use relative paths for linked assets (Blender's default) so the project opens identically on both machines.
Blender saves a .blend by writing a new file and swapping it into place, the save pattern KeibiDrop's tests cover most heavily. Work turn-taking on a .blend: one person saves and hands off, the other opens. If two machines save the same .blend at the same moment, the newer save wins the name and the other version is preserved as a conflict file on both machines.
Blender's .blend1 backup files sync like any file; they are your extra safety net, not a problem.
Render output written into the shared folder lands on the other machine on read. A render farm of two: the workstation renders into the mount, the laptop picks frames up as they appear. For command-line pipelines around the frames, see ffmpeg on remote files.
Point simulation caches, the temp directory, and preview caches at local disk, not the mount. Caches are high-churn scratch data; syncing them wastes the link and helps nobody. The project files and outputs are what belongs in the shared folder.
Blender itself is not yet in KeibiDrop's per-application test battery; its save and asset patterns are the tested ones. If you hit something odd, send a log.