Hi there.
The answer is the way OpenCore and Clover treats a DSDT patch rather than a secondary SSDT. When you create a patch manually you dump the DSDT of your PC and then search for the USB-relevant file. Next you re-write some of the code to match the USB spec you want. Then you "merge" it back into the DSDT on the fly. Try and find the "merge" option in OpenCore. It's not as straight-forward as Clover. Maybe its
beta status is the reason it hasn't yet been openly implemented.
An SSDT replacement patch
is the best way to configure anything because it patches ACPI before the OS gets going and no kexts or other possible security breaches are involved. macOS goes easy on it. The trouble is, of course, writing XML code in the proper schema is not easy for most of us.
Hackintool's USBPorts however is a rather special kext, just like USBMap.kext produced by another well-known Hacker and their script. It has no executable and thus is not fully "visible" to macOS. Run "kextstat" and see if you can find it. I have seen occasions where references pop-up but the point is, it isn't seen as a threatening kext. Show Package Contents reveals all. It's just an info.plist with code similar to an SSDT.
So there really is no shame in using USBPorts.kext instead of a patched DSDT. It isn't a second-class citizen. I wrote the new guide for USB using it because I knew Catalina was bringing new security and that this would only increase over time.