I believe this is a miss understanding of casting and the eventFilter structures.
If you think of the filter as a table with multiple rows, the first statement is about the results of a row.
Each row has one or more operand(s) and an operator (Like, And, Or, equals etc) Most of the Operators can only resolve to a true/False or NULL. A few provide another function and are used for amore complex operations. The end result is if an event is to be included in what is reported.
The cast applies to individual operands, and there is a table of types of casting is allowed, it clearly states that if something can not be cast to a boolean, it result in a null and rules for a Null apply. It is important to not mix that a cast is for an Operand (which is a parameter for an Operator) and each operator indicate what should be done and if it is allowed.
anything in the table that can not be cast is a null (NodeId in your report). An integer has casting rules -> zero (false) vs any number (True) - Only implicit conversion can be automatically applied.

we see no changes that are required to the specification.

Agreed to no fix.