So, I haven't modifed the turning paradym yet. That is a post 2.43 work item and I'll probablly make it optional for backward compatability reasons, perhaps even adding new sysvars for the new turn actions. Thus, values written .aimdx and .aimsx today are still absolute degree requests, not turning force requests. They accelerate, turn and decelerate all in one cycle. Bots can have and keep angular momentum even today (primarily due to tie torque actions) which may keep them spinning withotu action on their part, but voluntary turns do not add to angular momentum (although they will reduce it if the turn direction is opposite the aquired spin). This is broken I know, but its the best I can do at present without changing the turning paradym.
So, the way it is set up now, bots only get charged a turning cost for turns they make. There is no charge for aquired angular momentum. That is, a turning bot that is spinning due to aquired angular momentum will keep turning without charge. It's just that today, it's really hard to aquire angular momentum. A single voluntary turn request will not keep a bot spinning.
The turning cost today is proportional only to the amount of the turn and is not currently dependent on bot mass or radius. I will change this as you indicate, but doing so won't help the larger issue above.