Yes, basically those nodes should be updated to use the 'ignore' node type rather than not having one defined. It's a change that can be done now and will work with the latest release (and some previous ones). If not, after a future update up to the devs, those 'bad' nodes will cause an error rather than a warning suppressed error. Since this is usually tied with OXCE yaml anchor copy pasting, searching for any of the & tags can help locate them, however, not all '&' will be bad, just those without a the typical "type" node or one of the extended ones (including "ignore")
Edit:
This regular expression has worked for me to pinpoint 'bad' nodes in VSC. It covers the common node names but none of the extended ones. This merely means that some false positives might occur if the mod uses any of the extended nodes.
(- &.*\n)((?!type|name|id).)*$
Edit 2:
Tested it with Rosigma, but the only 2 flags aren't related to that line number.
The 1st one points to armors_IG line 2618: This one I'm not sure about since there is a 'type' node, just 3 lines down from it.
The 2nd one points to armors_PRIMARIS line 109: Again, 'type' is used, this time 4 lines down.
Now I'm really curious how that line that is triggering the suppressed error is defined.