We have a customized publishing workflow to restrict what/how/where users publish, and part of that workflow includes analyzing the map for any errors. In ArcMap, we would call arcpy.mapping.AnalyzeForSD, report any errors, and stop processing if needed. However, in ArcGIS Pro, we have to call arcpy.StageService_server, then report any errors. I'm not sure if that call short-circuits if any errors exist, but it seems to take substantially longer to process than ArcMap did.
Having a direct call to AnalyzeForSD would both shorten the time when errors are encountered and allow easier diagnosis on crashes to know whether analysis or staging failed. This has been discussed on Community, and even had a bug submitted. While the bug has been marked as "will not be addressed", I would implore a reconsideration, especially since the workaround listed is no longer viable.