> it actually exploits the spatial/temporal redundancy of the image stream to save render compute

This is great until the redundancy no longer exists and you have to rebuild the entire state machine from zero (a humble scene transition or rapidly turning a corner).

>exploits the spatial/temporal redundancy of the image stream

Gbuffers have been using motion vectors forever. For realtime global illumination, techniques like ReSTIR already allow for temporal reuse and spatial coherence.

I just don't see the purpose of replacing the traditional rendering pipeline for neural rendering techniques. It would be one thing if we were constrained on the number of triangles we could push per second, but we're not. The bottleneck is usually elsewhere in the pipeline: animating characters/objects, particle systems, physics updates, etc.