As an example I have use cases which are made more precise e.g. by activities, sequences or state machines.

To maintain the relation between the use cases the concretization I use the traceability matrix feature, but I need several of those, depending on the modeling language I have chosen for the concretization.

I faced the same problem. The workaround I use: 1. Assign a special tag to all relevant entities (of different types).2. Create an user search that finds all items by this tag3. Use the search as Source/Target in the relationship matrix.

Not sure if this would be a 'best practice' way of using use cases. Seems like you are trying to do functional decomposition (a flowchart, or a process hierarchy) using use cases? In that case activity diagrams would be a better option. Cheers!

However this issue is just such simple that I want to meet some basic needs about traceability.

E.g. to trace what modeling elements satisfies which requirements, or what modeling elements provide more context e.g. by scenarios to use cases.And those modeling elements are just of different kinds.

Assigning special tags to all relevant entities does not help me either.