The problem I’ve had is just how jarring the transitions are on refresh. I don’t need it to run continuously at 24/29/60/120 FPS, but I do want it to load the next page in like 25ms. So imagine it taking more power to update the display, but it still isn’t refreshing continuously so would hopefully still have power consumption advantage.
(Even a drawing application could maybe handle it if you could refresh subsections of the display)
At least for grayscale e-ink (Carta) displays they have this under control quite nicely. Full refresh isn't needed often, and when it's needed it's a fast rolling refresh rather than the traditional full screen blanking. Although I'm not sure if that is a reMarkable specific feature.
Ignoring the details of the physics and mechanics of how it would work of course :). My highest Physics grade was an NZ C+, so somewhere in the 55-60% range :)
(Even a drawing application could maybe handle it if you could refresh subsections of the display)