Changing the moderation state field translatability isn't reflected in the content translation UI and it's unclear what changing this accomplishes

each translation can essentially have their own moderation state associated with them

Having some trouble with this on nodes where we have set the 'Published status' to be untranslatable. This makes the published status sync between the translations, but the moderation state becomes mismatched. I thought I could just uncheck that too but am seeing what is reported here, it is always checked when the form loads.

Should the moderation state be translatable if the published status is not? I guess I can see how it still might be different but that doesn't make much sense in practice. Or at least, I think it is logical to want this to not be translatable.

#12 we had a similar requirement for one of our projects (to sync the published state across translations).
We investigated https://www.drupal.org/project/moderation_state_sync → but this creates tons of revisions so it is not ideal.

After some investigation if looks like moderation state is forced to be translatable (by design), and there is no easy way to get around it.
I came up with this, which instead of syncing makes the moderation state untranslatable, which prevents a revisions galore.
It seems to be working but EntityUntranslatableFieldsConstraintValidator gets triggered and I didn't have time to properly test it.

Eventually we abandoned the idea, for now. But it would be nice to find a solution for this.
Perhaps moderation state could work according to the translatability status of the published field? but perhaps there are implications.