The known sign of a save being corrupted is that at least one of the military equipment screen specific item lists have a nonsensical item in it (typically an artifact "book" with a very low item number). Thus, going though these lists and wrapping around to the end (by going upwards rather than downwards) should show you the junk items if they are present.
Thus, it's not hard to perform a manual check for the known sign (but it sure is tedious to do that again and again).
The problem here is that these lists are generated on the fly to provide data for the UI screens, and it's not known where their data comes from (i.e. these lists are not the source, but just generated to present underlying info that might be pulled from different sources). If we knew where the data came from it ought to be possible to write a DFHack script that scanned the source structures for corrupt items, and possibly even remove those items from the lists (to fix the bugged instance). I'm fairly sure the data doesn't come from the "normal" item lists identified by DFHack, as the corrupt items haven't showed up in them when a known corruption is present.
The crash itself happens when DF evaluates equipment for militia, so if you disband all militia and never assign any ever again the bug (itself) should not affect you. Assigning specific items does not prevent whatever processing that causes the crash from happening (a guess is that this processing is an attempt to compare the equipment, trying to accessing item fields that do not exist in the items that shouldn't be there, like e.g. the race the equipment is made for).