************************************
*** This is the actual Answer ***
************************************
OK I actually got to the root of the problem by calling VMWare support since my search for PSC services not starting on auto was not yielding any results on my own. After explaining the issue and trying to prove that the problem is that the PSC services are currently set to Manual and that I just needed the right commands on how to set them to Auto from the shell, they asked me to follow KB2151528 (https://kb.vmware.com/s/article/2151528#/s/article/2151528) which says the following steps
1. Run this command to check the start status : chkconfig -A
For example:
#chkconfig -A
You see output similar to:
applmgmt off
vmafdd off
vmcad off
vmci on
vmdird off
vmware-cis-license off
vmware-cm off
vmware-psc-client off
vmware-rhttpproxy off
vmware-sca off
vmware-sts-idmd off
vmware-stsd off
vmware-syslog off
vmware-syslog-health off
vmware-tools-services on
vmware-tools-vgauth on
vsock on
In the above example, most of the VMware service status is OFF.
2. If the service status is set to off, then perform these steps to turn it ON.
a. Run this command to stop all the running services:
service-control --stop --all
b. Run this command to change the service state from Off to On state:
chkconfig <servicename> on
For example:
chkconfig vmware-cm on
c. Once all the service status is set to ON, run this command to start all the services:
service-control --start --all
Note: Change the status of the dependent service to ON before changing the status of any service that you are trying to start. Attempting to change the status without changing the status of the dependent service will fail.
For example:
#chkconfig vmware-cis-license on
insserv: FATAL: service vmware-cm has to be enabled to use service vmware-cis-license
insserv: Service syslog is missed in the runlevels 2 to use service cgrulesengd
insserv: exiting now!
/sbin/insserv failed, exit code 1
So I used my Excell chops and created this list and pasted it a few times in the shell of the PSC until I got no errors
chkconfig applmgmt on
chkconfig vmafdd on
chkconfig vmcad on
chkconfig vmdird on
chkconfig vmware-cis-license on
chkconfig vmware-cm on
chkconfig vmware-psc-client on
chkconfig vmware-rhttpproxy on
chkconfig vmware-sca on
chkconfig vmware-sts-idmd on
chkconfig vmware-stsd on
chkconfig vmware-syslog on
chkconfig vmware-syslog-health on
And Voila! After a restart of both PSC and VCSA all is well again!