Actually it's backwards. Git gives ability to manage and navigate commit graph on quite low level using a pair of commands: checkout and reset and fulfill any wild desires. While in other VCSs it's a separate command per case.
Note: I think GIT UX is horrible and requires multiple years of practice to be comfortable with.
Most of the time, you only need a handful of commands, but there's a long tail of niche situations, especially if you are using git for maintaining a large project like the Linux kernel.
Remember, git was designed and written for the kernel first and foremost.
But it's used widely in projects that are not the Linux kernel. So what should they do, fork Git and create a LITE version? :)