The Petals Services view does not import a SA in the workspace.
It only makes its services visible.
My question is "what is the goal?". Why do you need to import several SA at once?
If the goal is only to be able to see the end-poins of the SA (to use them in a service consumer, per example), then the mentionned view is enough.
The import of one SA is already quite complex.
One upgrade could be to add a second button to select a directory in the SA import wizard.
And instead of proposing a list of projects to create, a hierarchy of projects would be proposed.
The hierarchy being a SA project, and under a list of SU projects, with all their properties.
This is clearly feasible.
The question, again, is why do you want to import several SA at once?
Generally, when a SA is imported, it is to be edited and reexported.
What would be the interest?
Have you tried with the Petals Services explorer?
=> http://doc.petalslink.com/display/petalsstudio/Getting+familiar+with+the+Petals+Services+view