Hey! I am not trying to hijack your thread, but I do want to alert you and any possible solvers working on your issue to my similar experience.
I installed a 3rd pty 2TB SSD a couple of years ago in my MBP. Bootcamp installed without issue and I have daily used this configuration. Unfortunately, the SSD crashed. The supplier (OWC) confirmed it was a defective SSD and replaced it with "an updated version", a "2.0TB OWC Aura Pro X2 PCIe MBx gen2".
I took the replacement drive to my Apple Service Center and they installed it, loading Catalina, but leaving me to load Win 10 via Bootcamp. Unfortunately, I experienced the loop issue immediately. I reinstalled Catalina and re-downloaded a fresh ISO of Win 10. No help.
I took my MBP back to the Apple Service Center and for the next 5 weeks we played a game of them uninstalling and reinstalling these two operating systems time and time again.
Finally, they gave me back my MBP and said I must have a defective motherboard. Because of the cost of a replacement motherboard, they advised me to buy a new MBP. (Which I might have done, but I like my MBP with all its ports. *smile*)
In frustration (I'm sure you now know the feeling), I contacted support at OWC. The tech told me that Apple had changed something in their code that conflicted with some parameter on my new SSD. He assured me it only affected the install and that if I could get Bootcamp to load Win 10, it would operate just fine.
I have tried everything, but to no avail. So I finally loaded Win 10 on an external SSD. However, now I am having issues with the external Win SSD interacting with the internal SSD.
These are my MBP's particulars:

Why I tend to believe the conflict issue mentioned by the OWC tech is because the Apple Service Center told me that the reason they suspected a defect motherboard was because if they put my new SSD in a different MBP, everything installed just fine.
Hope this helps (both of us and all the others out there).