When I've seen 3 tickets to our ticket system where the entire system was unable to function any longer due to installing git as a server (not as a client application but server-wide) on a cPanel machine, I will most definitely suggest to people not to install it on cPanel.
Good and timely advice aside, KrystalS is correct I'm afraid Tristan. Not installing GIT it is not a solution to the problem. It is merely an avoidance of a problem that sees cPanel break if you do so. Tour recommendation here may be the correct one, but the number of tickets you quote as reasoning for your recommendation only highlights this avoidance.
This is not to say that this problem lies solely on cPanel's shoulder's. Two systems can simply be incompatible. However in this case we are talking about what is becoming the biggest version control system in the industry. One that runs just fine on the very same server absent of cPanel. In fact it sounds like it runs just fine on the very same server WITH cPanel. It's just that cPanel runs the risk of not functioning at all. While GIT still hums along just fine.
It is this latter fact that makes it rather obvious that, although currently the correct action, simply not installing GIT is not any form of a solution. Hopefully that line will change and a discussion emerges (or has already). Because if not, the thing you are forgetting is the two systems are both heavily tied to the development life-cycle of their users, your customers.
And given the emerging prominence of GIT and Github, it's pretty hard to say which system developers and business owners will make do without for the benefits of the other. Given the vast distribution and adoption rate of GIT, I would be a little concerned with this incomparability if I were working at cPanel. Let's be honest, finding web server management software that not only doesn't allow you to use GIT even natively, but also may break your production environment in doing so, will be a bit of a WTF moment for many.