So, I was investigating this issue for a while and after some debugging of journalctl --user and dbus, it's possible to see that the gvfs-daemon.service was being started too early due to another tracker: "tracker-extract-3.service", which has WantedBy=default.target. This default value of default.target is graphical.target, and that is also too early for gvfsd to be able to get the correct environment.
So, after disabling tracker-extract-3.service, changing its Wantedby to gnome-session.target and then reenabling it, the gvfsd service is now started with the right environment.
So, I was investigating this issue for a while and after some debugging of journalctl --user and dbus, it's possible to see that the gvfs-daemon.service was being started too early due to another tracker: "tracker- extract- 3.service" , which has WantedBy= default. target. This default value of default.target is graphical.target, and that is also too early for gvfsd to be able to get the correct environment. extract- 3.service, changing its Wantedby to gnome-session. target and then reenabling it, the gvfsd service is now started with the right environment.
So, after disabling tracker-