Beyond that, getting a full path is trivial (realpath) and figuring out which block device backs it is also quite straightforward (findmnt).
There are also strange constructions that don't actually correspond to a single folder, or at least there were the last time I used Windows which was quite a few years ago now. A place that looked like a photo directory in Explorer, but actually it was a view of multiple directories and I don't know where stuff ended up if you copied into it.
The Explorer does not browse the file system, it browses a graph of (COM) objects called the “shell namespace”[1], and has been since Windows 95. Notable examples of non-filesystem nodes include My Computer, Recycle Bin, Control Panel, and Network Neighbourhood; a more obscure one is the All Tasks (“god mode”) collection of all settings applets that exists so that the Start menu can search it[2].
I actually think it’s neat how seamlessly this approach has been integrated—we don’t usually think about it even though we actually encounter it all the time. Microsoft’s attempts to extend this to a full-blown object-oriented (Cairo) or relational (Longhorn) filing system were always so muddled I don’t really get what the actual idea was, though.
[1] https://learn.microsoft.com/windows/win32/shell/namespace-in...
[2] http://brandonlive.com/2010/01/04/the-so-called-god-mode/
Contrast to windows where your "Documents" folder might be getting backed up via one drive or roaming profile, or it might just be local disk on that machine.
In my experience for a corporate windows environment its best to map a H: drive to a network home drive share and get users to always save in there - if its not mapped it means you are probably on misconfigured host.