Here's details of my current fix for this:
I have added a text field with the datetime string in it. (For conversion in the database.)
The command line code looks like:
MikeGale:
... -iTsFormat:"yyyy-MM-dd hh:mm:ss.ll.nn" -o:SQL ... "SELECT sTime, TO_STRING(sTime)..."
(I was expecting it to need the timestamp version of TO_STRING, but that didn't work!)
I then dug deeper and found that the documentation is unaware of timestamp2, though it does know about datetime, smalldatetime, date and time.
I guess one way to handle this in future versions would be to allow -oTsFormat:"yyyy-MM-dd hh:mm:ss.ll.nn" with a SQL Server output and intelligently handle the type issues, or just add timestamp2 to the recognised types and just do it.