It seems the content synchronization module syncs entities UUIDs, but not their entity IDs (like TID, NID, etc). Since it only does UUID, this can result in environments with mismatched IDs for the same entity.
Views filters based on entities filter based on the entity ID and not the UUID.
If your deployment target ends up having different TID than your view is filtered on, it will result in it being broken or showing wrong results.
I assume we can't be the only organization using the combination of the core config sync and the content synchronization module and so I'm curious how others are dealing with this issue.
Right now we're considering just copying the database over or maybe writing a script to update the IDs in the DB.