Hey Logan, to piggyback of what Heidi and Jon said, there currently is no way to publish a service that is pulling from a version as those branch versions now live at the rest endpoint level. This negates the workflow field staff have used in the past to make field edits send them back and then push to default.
Field Maps simply doesn't have the logic built in to switch to a named version while in the application. Further complicating this is the fact you can't have multiple editors in the same version. A lot of historical workflows involved field staff sharing a version. This made it much easier to review edits that came back in.
We have been inquiring about this since the release at 10.6.1 and haven't seen much movement. As Anne mentioned the only way to do versioned editing is to take the data offline--I believe this became available at the 10.8.1 release. It is a more involved process to manage this workflow as the administrator needs to ensure replicas are deleted. Deleting the downloaded collector map does not remove the replica.
I, along with others on this thread hope to one day see connected, real time versioned editing ability with branch versioning. It would also be nice to use a QC version which branch versioning does not support...