Unfortunately I don't know. It could very well have been that their own instances were being flooded by traffic from kbin.social and this was their solution. However, to my understanding this was added to the source code itself so all lemmy instances upgrading suddenly become an issue for kbin instances. I had to change the user agent in my own kbin instance to stop the flood of errors as it was absolutely messing up the.coolest.zone and I basically couldn't troubleshoot any legitimate failed messages.

Whatever the case is, I'm very glad it's resolved now.