There is a fundamental flaw with the practice of using the ValueType to indicate a Unit's symbol:
If the (UML2-compliant) option to also show the ValueType of a value property in Slots (and IBDs)is excluded by SysML, and if "secondary stereotypes" (11496) are not supposed to be displayed in IBDs, it in fact leaves no consistent way at all to indicate the Unit of a value shown in an IBD initial values compartment
because the Unit "metadata" belongs to the ValueType that types the defining feature (property) of a Slot !
In MD15.5 we have introduced the ability to show the Type on values in Slots and IBDs so we can now in fact communicate a Unit symbol well enough to engineers using the tool.