In the mean time we learned some lessons which I like to share here.
The first version of the demo tool was not able to copy UNICODE data between two systems. We extended the tool to handle this now correctly which is much more complicated than expected. The "challenge" is that a SCHEMA has to be defined and in case that you have a mixture of Latin and Unicode characters columns you need to define the unicode schema character lengths as three times of the table varchar field length. The disadvantage is that the overall row length remains at 64K. A bit complicated but this means finally that you can not copy all valid unicode character set tables with TPT. If the field length it too long the resulting schema will be rejected. I was not too happy about this - but maybe I just missed something. Would be happy to learn.
But also some new data types like geospacial data can not be copied between TD systems using TPT due to the UTD usage.
This lead us to the implementation of a simple copy implementation using ARCMAIN. It follows the same principle of specifying "only" a basic parameter script and the related backup and restore scripts will be generated and executed by the tool. To avoid data landing on file we implemented it with a named pipe solution which means the backup writes to a named pipe and the restore read from this named pipe. Both processes run in parallel. We integrated this into the existing demo script which is attached to the post. Some new parameters are defined and allows you to specify which tool to use.
The main limitation is that the two TD systems need to be on the same release (or the source system can be on one lower release - no arcmain copy from higher to lower release). In addition the arcmain solution can "only" copy complete tables and not subsets like the TPT solution. But the nice thing is that every table is copied (at least we didn't experienced problems in our test cases).
It seems to be worth to check the arcmain solution as this was 2 times faster than the best parameter sets for TPT.
For the main setup of the attached demo tool check the other blog entry and the containing documentation.
So keep evaluating TPT and arcmain to move data between systems.
Update: There was a bug on handling multiset tables. This is fixed in the actual attached version.