Correct, I strongly assume that the measures introduced at the API node to prevent the attack now also cause Hivemind not to receive the data reliably.

Interesting. So, the rate-limiting is too slow for hivemind to keep up(?). I have never learned to understand the hivemind architecture, but that theory is definitely consistent with the link, above. It still appears to be updating, but it's glacially slow. For example, when I glanced at it on the day I posted the comment above, it showed 8 rewards from September 10. Now, it shows 11.