Ouch, you do have both VINs stored diagnostically.
Address 01: Engine
Chassis Number: 3VWRZ71KX9M053902
Serial number: VWX7Z0H824L0Z9
Address 17: Instruments/Address 25: Immobilizer
Chassis Number: WVGBV75N79W526364
Serial number: VWX7Z0HN3NH0WE
What this means; Even if someone can build you coding that could be accepted (even if it isn't correct for the configuration) by the 03- module it will be rejected -or- zero immediately after you cycle the ignition due to the VIN discrepancy.
Because the Immo still has the proper VIN and I'm ASSumign all of the vehicle keys are original to the Tiguan all hope is not lost in regards to the diagnostic VIN discrepancy but I don't know if you can simply match that Jetta engine controller to this Tiggy cluster using at the dealer. If that's possible, the Immo defeat would need to be un-done and then someone with could run a Engine controller replacement test plan which
should transfer the Tiguan VIN into the Jetta engine controller.
However, as I type this I realized we've never attempted to encrypt Tiguan VIN digits into a MK60EC1 coding string. So, if that isn't possible - the above is entirely off track and it needs to go the other way making all diagnostic VINs match the Jetta instead. Because you cannot match used keys or clusters dealer level that direction would require someone with specialized tools or a complete transplant (lock cylinders, keys, cluster, etc) of the used Jetta components in which case you may or may not have remote compatibility issue but the VIN discrepancy could be resolved.
I would wait for additional feedback before making any changes. This thread would receive far more views in the Retrofits section however you aren't a
Verified user. Did you purchase that interface used?