Wait, what? The BVH construction / sorting triangles into buckets was still heavily relying in CPU?... You'd have expected that they had figurred that out 5 years ago?
I mean, once you have the BVH updated, then actually rendering any arbitrary size of BHV is a well understood problem, especially once we understood in detail how the traversal "engine" is essentially just a glorified LRU cache that permits spatial queries over its contents to find a much better entry point estimate than the root node (and often turning simple occlusion queries "for free").
Bingo. Framegen always goes hand in hand with an upgrade of the video decoding ASICs, and does not really depend on then tensor core performance. So this will most likely also scale almost effortlessly to the lower end parts of the 5xxx lineup.
3 frames worth of interpolation without noticeable stuttering will requires bicubic rather than bilinear interpolation though, so this most likely means that the optical flow analysis has gotten a 3rd frame (or a previous frames flow map) worth of input and now yields a derivative? Respectively it re-projects twice, which does still require a really accurate flow estimate in order not to get worse than the linear interpolation...