I have also witnessed this situation on arubaos 8.3.0.2, but there is a solution.
I tried setting SSH as "high priority" and as TOS=46 for example but here is no "h" in the datapath session and it is not sychronized to the other L2 cluster members.
I has used a rule as such
any any svc-ssh permit queue high tos 46 position 1
intially expecting that to work, but it did not....
i managed to solve the problem by changing the rule to this instead:
any any app ssh permit queue high tos 46 position 1
i believe this is not a bug but in fact how it should be working.
you must use rule type "app" instead of "access-control" to enable the "high value" feature set. Also, setting tos=x does not seem required, simply setting queue=high seemed to get me the desired "high value" determination.
I hope this helps
Neal Vadekar