I wonder if there is some benefit in ordering deployment based on the artifact type. I see benefit for config-admin property files to be deployed prior to bundles that need that config. A simple use case is to bootstrap spring application with cm-properties, where config admin entries must be present before app context start up.

Yes, you're right. In general, when the user needs to control deployment ordering, they either need to deploy artifacts in separate groups or, preferably, use a suitably structured plan which therefore controls the order in which artifacts are started.