Not sure what you're saying, but when the server determines the reliabilty needs to be reestablished, all new work fetched will be assigned with a wingman and thus if your copy is returned first, they'll show as PVal.

With PVer -mostly- a 2nd copy was sent off -after- your copy was returned as the server has determined doubt on current or a recent result of a particular science. Since FAHV is a zero redundant [like OET1], initially there will only be 1 sent out. Getting PVer when 2 copies have returned/computed is less frequent, and 99.9% of the time will result in one getting rated Invalid after the 3rd copy is returned. The one who gets the Invalid is bumped off reliability until that 20 odd series of valid has been done again. With any cache that in effect results in lots more requiring a wingman.

(Number of cores is irrelevant, except an 8 core in time will get that 20 Valid series much sooner than a duo. With 130 cores on FAHV having 150 in PVAL
and 100 in PVer sounds though as just being a normal verification cycle. See lots of PV for FAHV/OET, filter on error and invalid to see if kicked off by a specific device.)