I looked and it appears the reconcile and post process is already incorporated into our weekly compress database script using the ListVersions and ReconcileVersions commands. If I simply create a child from the default version to republish editable services from that, would that theoretically be all I need to do for an extra safeguard?
Also I have yet to figure if using the option to 'create version for each user' in the download offline options on the service settings might alternatively take care of the versions, however does that matter if we're normally always in a connected, albeit signed in, environment? Given recent drawing alert issues for staff connecting to the database, I'm curious if editing via feature services would alleviate the issue.
Thank you for all the helpful insight so far!