My guide DOES NOT use the port limit patch.
The fact: Using the port limit patch is not a long term solution. For reliable USB (assuming your ACPI implementation of _PLD and _UPC is broken... and you don't want to fix it), you must implement a custom SSDT for USBInjectAll.kext that configures your ports on XHC such that the port limit patch is not needed, and each UsbConnnector value is correct for each port.
I didn't say it did. I was referring to using the port limit patch to show all ports while you're performing port addressing, assuming it actually works with your system.
Your guide DOES explain the port limit as an implied option, however, just not a permanent one. The sentence bolded and underlined above implies it, especially if you already have a working port limit patch in place; I know because I did it. If the port limit patch works for someone, and they wish to implement your method, they should already be able to identify all their port addresses without using the -uia/uia bootflags. That's actually what I did to identify all my ports prior to upgrading to 10.14.1. Good thing I did, because 10.14.1 broke the patch, but it is still applicable for a lot of people. If their port limit patch works currently, and they wish to implement your method, there is no need to go through the bootflag process to get to the same end result, which is SSDT + USBInjectAll.kext (no port limit patch).
Again, I know because I identified all my ports when my port limit patch was actually active in 10.14, and I didn't need to use the -uia/uia bootflags. It may not be YOUR way, but it is a way. If the port limit patch isn't permanent (will be removed), it doesn't matter whether you use it, or not, to identify all your ports, as you will eliminate it once you have installed the kext and SSDT in accordance with YOUR GUIDE. As much as you claim the port limit patch is a problem, I've never had any issues with it or my USB ports, until it simply stopped working. So, I don't think people using it for a few additional minutes to identify their ports would cause any problems, like you claim. It's definitely worth explaining better, or adding as another option, in your guide.
No such thing as "-uia_include". No such thing as "-uia_exclude".
There is "uia_include" (used in the guide). And "uia_exclude" (used in the guide to exclude USR1/USR2).
Also "-uia_exclude_ss", and "-uia_exclude_hs" (both used in the guide).
I was typing the bootflags off the top of my head assuming he would read the guide for everything exactly, which is why I referred him to YOUR GUIDE. I stand corrected.
I didn't get a "Great!"