In 2.2.2 setting a status doesn't require any capabilities but in 2.3 (#538) we now have a can_set_status() method which checks if the current user can approve translations. This check fails when importing strings via CLI.
A side effect of this issue is that you might end with duplicate current entries because there is no capability check when the import creates the translation.
That's a back-compat issue and was noticed on translate.w.org. 🙁
To provide the same behaviour as before we could add a gp_pre_can_set_translation_status filter when WP-CLI is used.