Problem with i18n_string + features + sites with different default language
My solution:


Do not enable i18nviews.
Create all views with English strings.
Use the core translation system to translate all those strings.
Optionally, use features_translations to export translations.


I do not claim that this solution works for all cases where i18n_string assumed source language causes trouble. But in this case it seems to be sufficient.