Well, we can always just analyze the last frame, though it's not impossible for a camera to actually cool down, and there are other things besides temperature that influence behavior.
An ideal algorithm would probably pick a handful of frames and use all of them *together* to find stuck pixels, but such a complex algorithm is beyond the amount of free time I have to work on this project. Additionally, Resolve Lite is pretty much the only software that doesn't automatically take care of these anyway (and I don't use Resolve personally).
On a side note, from my understanding there's no real difference in "hot" pixel and "stuck" pixel, they are caused by the same phenomenon, there are just various levels of "hotness" a pixel can have. There does tend to be a non-linear response to the various parameters that effect them (temperature, ISO, exposure time, etc.), which gives the impression that some pixels are always "stuck" and some are only "hot", but really the "hot" ones are just on the more linear side of the non-linear response, and the "stuck" ones are past the "elbow".