There simply is no simple list of commands that you can copy and paste to "clone" a server or copy an old server's configuration in its entirety to a new one. Copying and pasting rsync commands in an attempt to do this most often causes serious problems, because doing so assumes that the old server's configuration is good and valid. That is a bad assumption to make, and the rsync process will simply copy everything over, bad configurations and all, and cause problems from the beginning on the new server that should be pristine.
The links I provided in my previous post explain how to copy the EasyApache build profile and most of the cPanel configuration. This can be done successfully. If you copy the EasyApache profile and /var/cpanel/cpanel.config and /etc/wwwacct.conf before installing cPanel, cPanel will install using the EasyApache profile and the settings in cpanel.config and wwwacct.conf.
You can copy the MySQL configuration, in most cases, by copying /etc/my.cnf from one server to another. This will only work well if the MySQL version is the same on both servers. If at all possible, it is best to make a MySQL dump, using the mysqldump command, of the databases on the old server, copy the resulting files, then import them into MySQL on the new server. This is far preferable to copying the /var/lib/mysql directory or its contents, which can sometimes work but is not advised.
If you have a hard drive with cPanel installed on it that will not boot, but can be mounted, you can actually use chroot to make that hard drive your environment, and then use cpbackup to make valid, good cPanel backups that way. The only thing this will not do is make backups of the MySQL databases, but you can even work around that by changing the base directory for MySQL in the my.cnf file on the old, bad hard drive. Of course, this does run the risk of copying over bad data if the hard drive has corruption, but it can make good cPanel backups that will restore on the new hard drive.
The best way to avoid all of these less-than-ideal situations, ultimately, is to use cpbackup to make good backups and store them in a remote location, off the server, so that they will be available to restore if the need ever arises. This will completely avoid the need to try to use rsync, chroot, or any other methods to try to salvage data after a hard drive failure or other disaster.