Kylie - I'll be attending the Esri UC if you want to have a follow up conversation about this.
My area of interest is in the Utility space where we're dealing with the constraints imposed by Branch versioning feature services. In terms of editing, one of the biggest constraints around this is that any versions (and therefore edits) created against a given feature service can only be seen within that feature service. So if I set up a separate feature service for Collector (or web editors) that only exposes a subset of the data to my editors, then when the data is being reviewed / cleaned for posting the reviewer will be limited to seeing the same amount of data.
This becomes incredibly important when you have field personnel collecting a subset of required information and require back office personnel to do a lot of the heavy lifting to get the data prepared. The way I handle this right now is by just using client side configuration to use settings on the layers (definition queries, field visibility, field highlighting, etc) to control these behavior. The challenge with the client-side constraints is that they are easily bypassed by advanced or malicious users. By enforcing these constraints at a service level I am able to safeguard against this.
