$env:PSModulePath Question / Potential Issue

I'm having an issue with Intellisense being very slow.

I've managed to whittle it down to VS Code loading modules over the network, so every time I hit tab, it goes off to the network share and does what it needs to do and then Intellisense works.

This can be up to 2 minutes at a time, however.

I removed the entry from $env:PSModulePath in the integrated VS Code terminal, fine, Intellisense is once again rapid and I can continue happily with my work, then around 30 seconds or so later, everything slows down again.

Lo and behold, the UNC of the file share is back in $env:PSModulePath! I've tested this in the ISE and do not get the same issue after removing the UNC share path.

Happy to submit logs if required, hoping there's just something I'm missing, however.

EDIT: It seems to be that when I hit tab or Intellisense trys to fire, it adds the UNC share path back to my $env:PSModulePath. Again tried with the ISE and don't get the same thing, so I believe this to be a bug.

SECOND EDIT: It appears to add the path back into $env:PSModulePath as soon as you click into the editor window.

Start by reproducing the report in the VS Code integrated PowerShell terminal: remove the UNC entry from $env:PSModulePath, click the editor, and trigger IntelliSense or Tab completion. Inspect the extension's handling of PSModulePath and module discovery, comparing the behavior with ISE. Done means the UNC path is not unexpectedly re-added and IntelliSense does not block on the network share.