Thanks for ideas, but believe me i've already thought of similar ways of merging all jobs. And that's no satisfying for me.
One hand, TDUCP intends to fix some mistakes in patch 1.68b. Now fixing over your pack is even more a challenge. Not knowing what changes you've made exactly. TDUCP fixes and adds data in many topics.
Other hand, how to proceed when lines of same ref have changed in both? Sticking to TDUCP changes will make UCP unstable. And vice versa.
Of course manual merging is possible but my decision is to get things the most automated possible. Whereas TDUCP and UCP impacts should be dealt case by case (if the words are correct).
And not the least important thing, TDUCP plans are huge, so it should evolve periidically. At every release, asking people to rewrite features based on the patch are not an option. TDUCP is a patch, so my objective now is to make it as clever and flexible as possible.
Now I don't wanna ask you to make your project on TDUCP2 base as it's too late and time consuming. TDUCP should have sooner replaced 1.68b to make it easier.
Btw, which was the issue in getting TDUCP db files to work on your rig ? Full version has all BNK files and does not require any tool/installer to be launched (patch HD is an optional feature).