There are various options depending on developer skillsets.
If you work with Java then perhaps you would consider offering the developer of the
Android app assistance. He was working on his app as a personal pet project but I think he got turned off when people started asking for changes - as happens to a Lot of FOSS developers. Unfortunately that app has drawn some criticism because it isn't fully compatible with Dan's ToDoList, and I fear the app functionality may reflect upon Dan's work even though he's not related to it in any way.
You could dabble with the TDL source but I don't believe the UI is modularized far enough away from the rules (MVC-style) to allow you to abstract your own version of the UI without significant retrofitting on every update from Dan. It's just not worth it. If you could plug Dan's rules into your UI on every update, you'd be golden, but that won't happen.
I believe Todoist has an API (one of the reasons I signed up with them too) but I haven't looked in a while. Perhaps you could work out XSLT to transform between the .tdl schema and theirs? (Or any other) That would be a valuable contribution and would allow you (for example) to make changes in TDL, save, auto-export to Todoist, use your data via remote/web, import back to XML locally, transform, then pull it back into TDL.
Another weird option would be to use something like WordPress or another CMS. Create custom forms and fields to mimic those of TDL and publish them on a private login. The data can be hosted anywhere you wish, shared server, private, whatever, it's all separate from the website. And again with import/export between MySQL and XML the data can be transformed to/from a .tdl. This could be done on each record update, triggering a transfer of the XML into a dropbox where it could be opened by TDL, with no special transformation effort at all. I could do this, if someone put a gun to my head, or enough beer and pizza in my mouth. The UI would be icky (um, comparable to the Android app?) compared to TDL but it may be better than nothing.
My vision for the Library is to do that transparently using OOP with established APIs rather than a more clumsy transformation approach. If some company offered to fund development for their usage, we'd all be Very happy. Unless that happens we all need to wait for "free" time where I can get this finished and published as a v1. Dove-tailing with the above, the Library is a quick vector to interfacing with a database (SQL Server, MySQL, etc), providing the transformation layer described for WordPress (Joomla, Mambo, Todoist, whatever).
So is your level of skill in various areas? Perhaps we can find some point where you can help to create this beast that you'd like to see.
T