Video frame iterator ETA not recalculating when load changes

[Informationator]

Information:

• Chainner version: 0.20.2
• OS: Win 10 Pro

Description
If my PC is under no load when begin running a chain, the time calculation tends to be pretty accurate. Let's just say it takes 6 hours for a given process. Alternatively, if my PC is already under load at the time I start the chain (e.g. I'm de-interlacing in Hybrid and encoding in Handbrake at the time), the estimate will understandably be much higher - say 24 hours. However, if I then pause the processes in Hybrid and Handbrake so that only chaiNNer is running, the remaining time will not go down to 6 hours. It stays high, but moves faster than real-time. In this case it'd go from 24 hours remaining to 23 in fifteen minutes, then from 23 hours to 22 in fifteen minutes, and so on and so forth until it's done. It never really seems to re-calculate the total time based on the current throughput.

Also, a minor feature request related to this: Adding hour/minute/second precision either as a UI option or as a tool tip (or both) would be great.

Logs
I don't have any at this time, but give me a shout on Discord if you need me to try reproducing the issue and we can coordinate. My tag is INTJustAFleshWound