General tag configuration bindings only execute at tag startup or restart, which is triggered by UDT parameter writes. Alarm configuration properties are more tolerant, because they have to execute when an alarm triggers in order to capture associated data.
Custom property bindings on member tags of a UDT simply cannot subscribe to live data changes elsewhere. For alarm properties, they execute only when an alarm fires. Not live.