That is not the case.
The answer to whether or not X is a derivate work of Y is the same regardless of the license of Y. It is answered by looking at how much of Y's copyrighted expression has been incorporated into X.
All the license of Y determines is whether or not, in the case that X is a derivative work, that making or distributing such a derivative work is allowed.
Some licenses have contributed to confusion over this by using terms like "derived work" or "derived from", which people confuse with "derivative work".
Maybe that was a bad example though, but do we really want to disallow opensource project from extending proprietary software without the blessing of the copyright owner? Because that is the other side of the coin.
Though for officially supported add ons system of proprietary products usually state what license you can or can't use. All kind of tools that access and patch process memory are not in danger because most of time they modify process state via 3rd party OS APIs and they do not interact with programs they patching.
In same time changes that patcher do within process can't go under GPL and fact that developers keep licensing that code under open source licenses doesn't change the fact it's break EULA.
GPL is opposite. It's clearly state that your code depend on GPLed code become derivative work.