RFC-388: Any workarounds available for the OneDrive issue with PSModuelPath until this RFC gets pushed to GA?

[JoelMiller74]

References:

• Let's move PSModulePath out of the documents folder PowerShell#15552
• Move PS content out of OneDrive #388

I am having more issues with being able to update or remove any PowerShell modules due to the OneDrive Synchronization.
I install modules to the default scope of current user because I do not have admin rights in my organization normally. I have to request it.
I have OneDrive enabled because it is our company standard and it ensures that I always have my documents and settings is something happens.
I have tried every workaround that I can to get around this for now until this change in RFC-388 is live but none of them work. I was close at one point by updating all psmodule paths to point to localappdata/powershell but since PSResourceGet is hardcoded, it ignored that and refused to use that.
If anyone is able to point me to a usable workaround until this is complete, I would be eternally grateful. I know it is on its way, but I also know it will take time.