Strange Alarm Setpoint Binding Dicsovered

I have been trying to update the methods used to grab alarm setpoints configured on tags and found this strange ‘bug’.

I want to run this by developers to see if I should be using this or if it is going to break on the next update.

I am setting up indirection to go to the following path:
The referenced variable is simply a string representing the path to the tag. I have confirmed that this does update when the value of the configured alarm changes.

Please advise if I need to come up with a different method as this property is not actually listed on the Tag Browser.