This is a new feature we added to detect and prevent null pointer exception. the engine compiler is inspecting the rules to see when a variable is used but not initialized which is going to generate issue at runtime.
All those variables need to be assigned a default value if none is assigned later.
We do recommend addressing the root of the issue, however there is a system property that you can set in Rule Designer and Decision Center JVM to prevent the check: -Dcom.ibm.rules.engine.variablesetinspector=false
https://www.ibm.com/docs/en/odm/9.5.0?topic=designer-ruleset-archive-errors
Are those variables declared as input parameters in an operation? In that case the error should not be thrown as the engine expects those variables to be initialized at runtime. I would be interested in looking into a sample reproducing those errors.