For maximum backward compatibility, the fix could be disabled by default. But enabling by default still provides a path to backward compatibility with a small amount of manual work for those who need it.
For those who don't want the broken behavior, it might be a hassle to have to enable the fix, but that's still much better than not having a fix and having to write crazy code as a workaround.
I don't know VBA, but as a guess, the #Const directive (https://docs.microsoft.com/en-us/office/vba/language/referen...) for compile-time constants looks like it could be a reasonable way to implement a switchable compiler fix.
Most people weren't using 64 bit office until it became the default in 2019. Companies using any sort of legacy add-ins may still be using 32 bit office in 2021.
It's very unlikely that there's much VBA code relying on this specific broken behavior in 64 bit versions.
That noted, a broken IF statement does seem like a very serious compiler bug. And especially since the correct behavior occurs on Macs, I think a fix is necessary. The language should be consistent across all platforms at the very least.
1. The person who posted the SO question said they rely on it. There are probably more who haven't discovered they're affected by this or who haven't spoken up yet.
2. An average VBA developer might be more likely to do something like this than you would be.
> and also it blocks a migration to Office 64 here, because we can not get our code out