Sorry, severity should be "feature".

The progress report could read: "now: xx fps | avg: yy fps"

So, fpr each processing instance (when ingesting one movie) DCP-o-matic would have to store: beginning and end time and frames computed. Maybe also the render config: machines available for processing, with their respective stats. But I'd give the latter a lower priority as this aspect is definitely more susceptible to fluctuations.

You're right, the current calculation is frames_remaining / current_fps (see remaining_time() in src/lib/transcode_job.cc)