Simplifying it to the UCCNC and neglecting what board it is, it is a single input pin for the UC300ETH module and for the UCCNC.
So, if that pin is configured as e-stop input and if it triggers then the UC300ETH motion controller triggers the e-stop logic of the software.
Because it is a single input pin in the UCCNC it can be easily seen if the problem is in the UCCNC or on the board, because if the input pin triggers (input LED on diagnostics window goes to active state of configured e-stop input) and if the software does not trigger the input then the issue is in the UCCNC otherwise if the input pin trigger triggers the e-stop then the issue is with the board or with the wiring.
And by asking CNCroom I thought about you emailing him, would be probably faster...