Probably, since it uses a very different way to implement viewport-only rendering, and is thus unlikely to have the same bug.
I’m aiming for a useable release late this year, but yeah, hard to say how that’ll go, since there’s still some fundamental design work ongoing.
That might help work around this issue. Shouldn’t be too expensive. If you can set up a minimal demo that reproduces the problem I’d also be interested in taking a look. In theory refresh should be enough to clear all cached values, but here it seems that’s not happening.