Not sure, but it would probably involve the main cPanel script, which is binary and cannot be edited without breaking the license agreement. Plus it would be overwritten on the nxt update. You could always edit the pages and remove the tag <cpanel Serverinfo="servicestatus()"> and insert your own status call, or just replace it with static content:
Server Status:
All good <green ball.gif>
If the server is down, the status page will be down.
Or change the link to open your own custom status page
Also some of those version labels are editable just by editing the config file - apache is anyway, but changing the label can break other things. Changing the Apache lable seems to not work well when running mod_security.
***
Locate status.html
/usr/local/cpanel/base/frontend/monsoon/servicestatus.html
/usr/local/cpanel/base/frontend/monsoon/mail/changestatus.html
/usr/local/cpanel/base/frontend/monsoon/cpanelpro/changestatus.html
/usr/local/cpanel/base/frontend/monsoon/status.html
/usr/local/cpanel/base/frontend/x/status.html
/usr/local/cpanel/base/frontend/x/mail/changestatus.html
/usr/local/cpanel/base/frontend/x2/status.html
/usr/local/cpanel/base/frontend/xmail/status.html
/usr/local/cpanel/base/frontend/xmail/mail/changestatus.html
/usr/local/cpanel/base/frontend/xcontroller/infostatus.html
/usr/local/cpanel/base/frontend/xcontroller/menu/info_status.html
/usr/local/cpanel/base/frontend/xcontroller/boxtrapper/changestatus.html
/usr/local/cpanel/base/frontend/bluelagoonadvanced/servicestatus.html
/usr/local/cpanel/base/frontend/bluelagoon/status.html
/usr/local/cpanel/base/frontend/bluelagoon/trunk/status.html
/usr/local/cpanel/base/frontend/default/tests/servicestatus.html
/usr/local/cpanel/base/frontend/Xskin/status.html
