I haven't tried it, no.
But honestly, if the battery is bad, the problem should be there when NOT using TouchBIOS also; it isn't.
The problem is 100% reproducible, and the longer I have TouchBIOS open before saving+restarting, the longer the clock is set back, quite possibly meaning it reads BIOS settings on program start, including the clock, and upon saving, it puts the time of launch back in the BIOS.
Makes perfect sense. Although, if I may say so, it seems like a newbie mistake that shouldn't ever have slipped through testing. There are also still some random unhandled exceptions crashing the app, but I won't go into that here.
What I can't get my head around, though, is that I'm apparently the only one having this problem. I can't imagine it would be difficult to fix either, since I guess it would be relatively easy to skip the reading/writing of the clock to/from BIOS entirely - I mean, you can't even adjust it in the app in the first place.