You can edit your posts.
The bot is converting all the sessions then hunting down "interesting" bits to clip. Remember, it's acting as a client itself, so it has its own log with its own session start times, which won't correlate with yours. So the time is then the session start time plus an offset into the session. AutoJAM used to split these two parts out but NINBOT combines them. I guess the Ninjamer bot does it like AutoJAM, though: YYYYMMDD_HHMM_MMSS, where the MMSS is the offset from HHMM into the session.
If you find a session you like, you work out what local time it relates to then find the session folder that has the nearest start time before that. It's probably the only way you'll get close.
Is it really still taking that long? Here it took 1 minute 17 seconds to convert a 37 minute, 14 tracks jam from a 92K clipsort and 1,327 Files (2.39 GB). That's on a disk that's about 35% full and recently defragged with PerfectDisk and using Reaper x64 on Win7 w/AMD2+ Quad Phenom 2.3GHz, 4GB DDR2 RAM. However, like I said, it's heavily IO bound with that many files. CPU looks like this: