Yes, I would assume so. At least just from a glance, not looking into the complete design.
The mid-left squiggle is probably just too cramped to get more vias in there. Your screenshot doesn't show the component placement but I'm guessing there's simply stuff in the way.
The frequent vias really don't matter here, as they're spaced close enough (the 'S' aside) to give a cutoff of some GHz, maybe 10GHz or so. (That is, for the vias stitching traces, the loop length corresponds to a folded dipole or slot antenna structure, with a cutoff somewhere up there. For vias stitching planes, they act as the sidewalls of a very shallow waveguide, so, the impedance is quite low to begin with (due to the wide aspect ratio plus dielectric loading), and also the cutoff is quite high. (Also the transmission rate is quite low, because FR-4 is fairly lossy up there; but that's not too important here.) Down at frequencies relevant to the converter, any possible error due to currents flowing in these loops will be reduced asymptotically from their resonant figures -- that is to say, if a given pair of vias and trace or plane is resonant/transmissive at say 10GHz, then it'll be ballpark something like -60dB at 10MHz, and so on. (For a waveguide it'll be worse than that, because the transmissivity is a length weighted figure. But we can model a simple trace loop or whatever as an LC circuit, in this case where C is small enough to ignore so the L is all we're really concerned with.)
I suppose, with a SAR (huh, didn't know they made SARs in that many bits -- impressive -- granted, I haven't shopped for fast 24-bit converters at all, either), this
will be highly sensitive to noise at a rate comparable to the clock frequency (or sampling aperture, or anything else relevant), so such a degree of stitching may well prove fruitful here -- ordinarily this would be complete overkill for anything other than RF, but the thing is, when such microscopic (indeed nanoscopic) errors can be detected, even the tail of that below-cutoff stuff can matter.
Anyway, it's also not that there's a whole lot of noise on those traces in the first place, or probably the planes either, and the ground (guard?) traces inbetween them is just an exercise in [gestures rudely].
To be sure, you'd have to model it in some reasonable way (this could perhaps be SPICEd, but you need to represent the board somehow, even if just local regions of it -- and test that against expected noise currents and paths, and determine whether the generated voltage is enough to worry about; else, a full-field simulation could be done, at significant expense, e.g. HFSS), or build multiple variants of the board and test them.
Likewise the middle-right hook-like section without guard traces, is probably just because there's not enough space to do it otherwise. maybe that would be better routed on another layer, or differently at all; which... looking at it, actually, the area is surrounded with the one-from-the-right pour on the top, right, bottom and left edges, and only a few vias are picked up scattered in the middle by the rightmost pour; perhaps it would be better with a direct route (notice no connection is made on the horizontal or vertical sections on the way to the middle of this (FPGA?) component!); and perhaps some (GND or signal?) vias could be moved around to get a wider route, escaping through the top-right corner of the component (where there's one lone via -- but more width already than where the top-left via is surrounded by unconnected vias, making an even tighter choke point there!).
Even this, I'm guessing, doesn't matter much; if that's an FPGA, then that's probably Vcore or something like that, where ripple might cause timing error (jitter), but nothing important for analog purposes. I'm also guessing they have bottom-side bypass caps studded around the thing, as is the usual style; so that the route length for this pour doesn't matter very much, anyway.
The one thing that does stand out, is that fat trace in the middle (hm, also why is it solid black?); that usually reflects poor routing decisions, or just an outright shortage of layers. But if it's away from sensitive signals, and it's well-filtered power or something, y'know, and not causing trouble for where it's cutting through (which, probably not, looks like that pour only connects to two pads at the center mid-bottom there?), then yeah, who cares right.
...Actually, what the hell is that middle pour even doing? It's got five vias up top (presumably power (LDO thermal pad?) and bypass cap?), I don't see anything else along the way, and then two pads all the ass way at the bottom. Could this not have been routed on the bottom layer or something, as an ordinary trace? If this is right under the ADC, surely it would've been preferable to leave this area just, like, GND on several layers or something? Weird...
Well, presumably this board is getting the full capability of the chip, so it's not like these are fatal errors -- like I said, the stitching is generous, presumably the bypass/filtering is adequate, and the component placement is probably good enough, so they're not exactly throwing away LSBs with this kind of stuff. It's more of a style thing, and it's really just a bit perplexing seeing so few connections to a pour, why allocate it at all in that case -- but again, I'm just looking at the one layer here, maybe it's deep enough in the stack that it doesn't matter, maybe routing on other layers sucked anyway, etc. The kind of design decision that's less elegant, more cromulent.
As far as outside (top/bottom) pours -- these aren't usually of much value to begin with, because the lateral (edgewise) coupling between traces or pours on outside layers is quite modest. That is, consider two parallel microstrip traces, with say 7 mil dielectric to inner plane, and 7/7 width/space for the traces. This gives a coupling factor something like -- y'know, I haven't looked this up in a while, do look it up if you need the exact figure -- ballpark 15 or 20%. That is: for example, if you look at the normal mode vs. (differential mode / 2) impedance, of differential microstrip of these dimensions, you see differential being only some percent less than the normal mode, or than similar geometry of a lone microstrip trace. This says that the traces predominantly act alone, and the coupling between them is only modest. (So it's kind of a myth to call it "differential routing", but it's not actually important how well coupled the traces are, as long as they're length-matched over any disturbances they might pick up -- differential routing is more about canceling noise than any particular matters of common-mode impedance or coupling.)
So, likewise the case for microstrip vs. CPWG (coplanar waveguide with ground -- microstrip with ground poured around it), for similar dimensions with/out the same-layer ground, the impedance is only reduced by a modest amount, say 10 to 20%. Which is what we're looking at here [I assume], with ground poured on top/bottom, around traces or components (pads).
The other things such pours do for you, is: reduce the general ground impedance (there's more thickness of metal in the ground net), and provide a slightly nearer sink for external fields (i.e., it improves shielding modestly). Consider the case of a microstrip trace in an externally applied electric field: some field lines terminate on the trace, most sink to the ground beside it. Well, if the ground were slightly higher up (on top of the dielectric, rather than buried under a little), slightly less field would terminate on the trace -- that is to say, less E-field couples to the trace, improving shielding. A similar argument applies to external magnetic fields, blocked by the adjacent metal; the vulnerable loop area is already quite small (thanks to the shallow height of trace above inner ground, like the 7 mil dielectric as earlier), so this only reduces it modestly, but it definitely does provide a reduction, so may nonetheless prove worthwhile.
And if nothing else, I suspect it's more just a style thing, you know, it's this fancy converter with a shitload of bits, might as well guild the lily right? No one's getting fired for pouring copper around the thing and taking a few extra hours stitching it, but managers aren't going to be happy if the thing is weeks to months behind schedule because it fails to produce the required ENOB / dynamic range / accuracy, or pass EMC (or both at the same time).
Tim