So are you getting it figured out? A simplified approach I like to take is like this (modified from your example):
ns=1;s=[{DeviceName}]P{MotorNum}_VSD.{Tagname}
As long as you name your UDT member tags the same as the PLC tag, you can copy/paste that tag over and over and only modify the name, data type, etc and the OPC item path binding is the same between them all.
One other thing to note is that it looks like you're using PlantPAx. If that's so, then you'll also need to modify your AOIs by exporting all of them to L5X, then doing a search/replace for:
ExternalAccess="None"
with
ExternalAccess="Read Only"
Then re-import and overwrite the AOIs. (Do this with all your AOIs actually even if not PlantPAx).
Then you'll need to buy the Ethernet/IP Class 3 Generic Client driver from @pturmel. Set all of your tags to read at the fastest rate you want (like 1000ms) - Don't break them up with leased tags or different tag groups running at different rates. (This sounds counter-intuitive, but trust me on this).
If you don't use Phil's driver, then you're going to only want to read the bare minimum required, and you will want to use leased tags for anything on faceplates, and read all strings at 60,000ms or slower to help with communication load on the PLC.
How do I know this....I'm currently in the process of helping a customer who was handed a PlantPAx programmed PLC with Ignition running at a whopping 8-second update rate for tags. With optimization of tag groups, I was able to get the HMI updating at a 2-second rate, but the PLC Class 3 comms were still maxed out at 100%. Switching to Phil's driver and setting everything to update at 1 second direct (no leasing/driven tags) and all 70k+ tags are reading at 1.1-1.2 seconds consistently. Our client instantly wanted to buy the driver for all of their plants, and I literally just bought it.