Exactly... the profile/stereotype approach works well for me...
I include several tags such as Severity (if not available to user), Frequency, Priority, Risk (to the project plan), etc.
Also, since I do a fair amount of automation/add-in prototyping external to EA (using Access), I have created several tag values that I use to "derive" information from the model, then update these tag values, that I can then use to modify specific elements..
Example: Derive target precision level for a UC (how fully dressed SHOULD it be... based on other tagged values as described above...), then derive the current precision level (against my business rules), then color code the use case elements to indicate how close they are to meeting the target... e.g., White (PL0), Pink (PL1), Yellow (PL2), Aqua (PL3), and Green (PL4) or when the Current PL = Target PL...