When you create a tag based alarm in the PLC, you can access all of the alarm settings and state with the @Alarm keyword.
If you have several alarms tied to the same variable(or AOI instance), you can then monitor the state of all alarms through the @AlarmSet keyword. The issue is that this functionality isn't described by Rockwell in any detail so it's a bit of a hit and miss. Also, since you don't get access to the internal logic of PlantPAX5, you can't see how they're supposed to be used in the PlantPAX5 topology.
I've asked Rockwell for help on this, but they are true to their fame and told me to Eff Off, but in nicer words. I do have monthly meetings with them about all sites in the company and am planning to drop the bomb in one of these meetings that I don't think it's worth continuing to integrate such a limited platform when we get more bang for our back with even Emerson.
Edit:
In your PLC, create an Analog Value tag. Then right click and add alarm, add the alarms for Hi and Lo (the creation menu has these options). Then in logic (the @Alarm doesn't show in the tag database), create dummy moves to see the values of the different members of the @Alarm UDT for each alarm. Play with the value of the variable to see the difference in data on that @alarm tag.
PlantPAX5 does make use of this functionality... however, they don't make use of the High and Low Alarms and instead configure all as digital alarms (which again is typical Rockwell to make something that isn't usable). My gut feeling without seeing the logic is that they don't have gate functionality in the tag based alarms and have to do it as digital to be able to implement the tag. But I may be wrong on the reason, doesn't matter.