Well, there are two parts to it, both of which are already noted. The first is that Max works pretty well, as you don't start IR and find your IR is two screens wide, which is totally unworkable, so you need to stop IR, change your final render resolution, start IR.... then you start your final render, and realize it's too small, so you go back to render resolution and set it to final. This is a problem unique to C4D, and super irritating (it's the one thing that gets me every time).
The other, about being able to have a super large render that is beyond the size of the VFB currently doesn't exist in Max either, but that is being looked at with requests for locking resolution etc. There is the problem that if you are rendering a 4K image, IR is going to be that much slower, but if the same functionality of "zoom in and you only process what is currently in the zoom" (which currently happens) is still there, well that could be fine for looking at small details.
The two are different issues, the first I find more annoying as it always happens in C4D no matter what you are doing with IR, making IR somewhat irritating when it should be pleasant. The second is a further improvement on IR in the core overall, not in Max at present, but being looked into (but it still wouldn't resolve the first one :) ).
EDIT PS - I also wouldn't want NOT to have the first solution, of IR resolution is the size of the VFB and always have it at final render just scaled down to fit, as I'd still then have a much slower IR than I would want. Hence, two issues, two things that would be good to see in IR :)