This comment has been minimized.

If its useful, I had RealVNC'c VNC Viewer.app on both these machines as well. It could be TigerVNC launched on a new user account because VNC Viewer.app had never been used in it and initialised that folder. Not sure if was a similar circumstance to @h3adache .