Long pre-heat period with reasonable print time estimations?

[zapta]

My gcode files includes a 1 hour preheating time that is injected by the Prusa Slicer's custom gcode (holding the bed at 100c to let the heat the chamber and stabilize the frame). This works well but makes the time estimations of the RRF significantly less accurate.

Is there a way to let RRF know about that heating period such it can handle it correctly in regard to the estimations? E.g. basing the estimations only on the behavior after the preheating period?

[Phaedrux]

As a work around I'd probably remove that warm up from the job and just do it manually.

[zapta]

Thanks @Phaedrux.

I like the automation aspect, that is, one click in the browser and a printed part a few hours later. Any creative idea for an automated workaround?

Or, should this be a feature request?

[Phaedrux]

I do my preheat in start.g but it's only a few minutes, not hour. I can't recall off hand if the time taken in start.g is applied to the total print job time.