I disagree with your summation.
Which part? Gatekeeper is part of launch services. If you're actually a developer and you want to correctly open external executables, you can execute them with launch services and gatekeeper will kick in. If you just fork/exec or spawn something, of course gatekeeper isn't going to kick in.
But like dozens of people have said, the app can do anything it wants once you agree to it, including launch apps. You're agreeing that you trust this app because it has an identity attached to it, that's all gatekeeper is.
As an example, download VLC, open the DMG and drop it on your desktop. Now, if you double click that with gatekeeper on, you'll be blocked (in the default setting). However, if you simply execute it, it will just launch. Open a terminal window, and run `~/Downloads/VLC.app/Contents/MacOS/VLC` and it will start right up. Finally, invoke it using launch services (either using the framework, which is a bunch of work since it can't present the gui and will just fail), or again, using terminal, `open ~/Doanloads/VLC.app` and you'll see gatekeeper block it as expected.