I know this has probably been said before, but CSM makes the whole applying maintenance process a lot easier. It will find all relevant PTFs depending on the FMIDs you've installed, chase all the pre-reqs, and offers time-saving options like FIXCAT to get all associate maintenance for categories for example to apply fixes related to a new z/OS level. You can even set up a schedule to automatically receive maintenance on a regular basis so it's ready for easy review and apply processing.
For me the bigger concern is what happens after, because you still have to run through the configure process (BC1JJB03) and install/retrofit your custom tables, Jcl and skeletons. I think a lot could be done to improve the automation and flow in this area, and I don't thing the answer is either CSM or it's successor MSM.
Either way I think it's important to include in the data collection HOW you are collecting and installing maintenance (ESD or CSM) and then WHAT processes you have to configure and deploy?