UML14 — Why is "FinalState" a separate metaclass ?

State Machines:

Why is "FinalState" a separate metaclass ?

It seems that a final state can be modeled as a kind of PseudoState
(with PseudoStateKind = final).

FinalState has no attributes of its own, and all associations inherited
from State must be empty for a final state:

• A final state cannot have an entry action
• A final state cannot have an exit action
• A final state cannot have an doActivity
• A final state cannot have a deferrableEvent
• A final state cannot have an internalTransition

Could anybody explain the reason of existence for a FinalState metaclass ?

declined