I had that problem as well. I wrote a really complicated macro to solve this:
- It uses a second temp sensor to see when the temperature on top of the bed stabilizes. If its already hot & stable the wait is quickly bypassed.
- It pauses the print while it waits which leaves the machine interactive. If you hit the resume button it will continue with the print. Everything runs in a background task to make this work.
I think you are more describing “state” vs “settings”. One of the difficulties with using a saved variable as you describe for this is that the state degrades over time. If I shut the printer off over night, or don’t print for an hour, its no longer hot. Saved state is only good if I have some way of validating that state is still accurate. And if I can do that, I can probably measure the state directly.
Lastly, but maybe most importantly, why did you restart the printer? If we could reduce the number of restarts maybe this is less of an issue. My most frequent restart cause is editing a macro. I keep meaning to give DynamicMacros a try.