Symlinks via NFS being resolved differently than SMB

Firstly, I am unsure this is actually a problem with Kodi, and as such this is may be more of an information gathering post. Before detailing the problem, a little about my setup:

• Media Storage:
  • Synology DiskStation DS1821+
    
• Android Clients:
  • Galaxy Tab S9
    
  • Galaxy S9 Plus
    
• PC Clients:
  • Windows 10 PC
    
• Kodi Version:
  • 21.2 Omega (but have tested this going back to version 19)
    

I do a lot of full disc blu-ray Iso's (i prefer to store my media this way as I like having the menu experience of physical media). As such, there are times where there are multiple movies on a single disc. I keep all of my movies in separate folders on my NAS and to solve this problem I create a folder for each movie on the disc and use symlinks in said folders pointing back to the where the actual ISO file is. Here is a simple example of what a path structure would look like:

• # This is the real iso file
  • /Video/Movies/Movie A (2000)/Movie A-Movie B.bluray.iso
    
• # This is just a folder containing a relative symlink to the iso in Movie A, using a command like 'ln -s "./../Movie A (2000)/Movie A-Movie B.bluray.iso"'
  • /Video/Movies/Movie B (2001)/Movie A-Movie B.bluray.iso
    

Now the above setup works great when I am using the SMB protocol to connect to my NAS. However, for reasons I wont get into in this post, I have needed to switch to a different protocol and am currently trying to use NFS. The problem is when Kodi scans these folders containg symlinks for content, the symlink path is fully resolved which ends up causing duplicate titles to appear in my library instead of the intended Movie A and Movie B. To further clarify, When scanning the folder containing Movie B for content, the paths are resolved as follows:

• ​​​​​​​# When using SMB protocol:
  • /Video/Movies/Movie B (2001)/Movie A-Movie B.bluray.iso
    
• # When using NFS protocol:
  • /Video/Movies/Movie B (2001)/./../Movie A (2000)/Movie A-Movie B.bluray.iso
    

Because it fully resolves the path when using NFS, the final Folder in the path ends up being Movie A instead of Movie B, causing the duplicates. So my question is does Kodi do this with NFS because of quirks with the protocol itself? Another thing it seems to do is fully resolve Hostnames to IP addresses when using NFS. So if I add my NFS server by DNS name, Kodi will find it just fine but when scanning content from that source it resolves the DNS name, making the paths to my video files which I would expect to be this:

• ​​​​​​​ nfs://synology/Video/Movies/Movie B (2001)/Movie A-Movie B.bluray.iso
  

to this:

• ​​​​​​​nfs://192.168.50.85/Video/Movies/Movie B (2001)/Movie A-Movie B.bluray.iso
  

This is frustrating because when I perform library operations on the source, such as removing the source and selecting the option to remove library items associated with that source, nothing is removed and I have to do a Clean Library option and manually delete every title. Is this another quirk with the NFS protocol? Thanks for any information.