If it really was that simple, mastering a new VCS would take 5 minutes. But it isn't.
If you need to branch, you also need to know how to merge. Then you'll need to know how to resolve conflicts. You probably need to know what branches are there and how to diff them. And since you know how to check in, it's just a matter of time before you'll need to know how to revert. That's just you alone - once you collaborate with someone else, you'll need to learn how to share code, push, pull, remote branches... There's a reason why your VCS has more than four commands.
The only things I need to know are how to check out code, check in code, label and branch. Occasionally I create a repository. Rarely.
If you gave me a GUI that just had those four functions, I wouldn't give a rat's ass what VCS was living under the hood.