There is no need to rush this hard-fork... Fuse will need a day or two to double check the code.

At this point, no one is going to use this exploit against KDC... at a network hash-rate of less than 100Mh/s... a straight up 51% attack would be easier and a guaranteed success compared the aggro of a using the KGW exploit. The exploit is most attractive for attacking networks where a 51% attack is not possible, because the KGW exploit only needs about 10% of the network hash-rate to be effective, so it makes the big networks vulnerable.

In the case of KDC, a 51% attack is instant and effective... and not much hash-rate would be needed... in fact... I could launch a 51% by myself at the moment with ease.

So more important to take the time to ensure the fix is implemented properly, add a few checkpoints, and make sure the hard fork is deployed after a considerable publicity and notice to all exchanges, merchants, users, and miners than rushing it because of the fear of being exploited.