I do wonder if we could make --explain better... I like to imagine passing --explain <u32 hash> to cargo check would supress all errors except for one with that hash, and provide relevant expansion of it. This may be just a symptom of rustc not having something like the go compiler's "too many errors" error, though...
(Errors, of course, would have to include a note with the --explain hash...)