Let your distribution do what it wants unless you're sure you know what you're doing. The fact that you need to ask this question shows that you don't know enough. So leave well alone.
Which programs need to be setuid depends on how things are set up on your distribution. For example, Fedora has replaced most uses of setuid by setcap. For example, ping needs the
CAP_NET_RAWIO capability to be able to open raw sockets; it can get it by being
setcap CAP_NET_RAWIO (better privilege isolation), or by being setuid root (the traditional method, which doesn't require setcap executables).
The programs you list are designed to be executed by ordinary users but require extra privileges to function. If you remove their setuid bit, you will break your system. For example,
ping will just stop working (unless you're logged in as root). You will be able to become root with
su but not with
sudo, which defeats the whole point of
sudo. Users will not be able to set crontabs. And so on.
On a dedicated server, some of the things that you've broken might not matter. But you should only change the distribution's defaults if you know that you're doing the right thing, not the other way round. Remember that availability is part of security. If you lock yourself out of the server or make yourself unable to diagnose and repair problems, you've broken your own security.