Let me explain how we are doing it for normal AEM pages.
We have base site under en local. We then use MSM to rollout the site to other locals. We then provide the rolled out local pages to clay-tablet for translation. We would like to achieve the same for content fragments if it is possible. But as you said content fragments are assets in nature they can not be rolled out.
So generally do we roll out the content service pages?
In your initial question you mentioned "would like to rollout the fragments to other locals" that means translation. So content fragments are assets in nature so they can not be rolled out individually if that's what you mean.
Please provide the version including the service pack. The reason is to verify if a known issue has been fixed in a certain fix pack so we know if you have the fix in your instance. Also I am assuming the template a an editable template (?)
for translation we are using clay tablet and are able to create different language copies for content fragments.
My concern over here is when I am embedding the en language content fragment in content service page and rolling out that content service page to different locals, other local pages takes the en language content fragment only. Anyway to change reference to point to particular local content fragment?