Imagine one person given the task of rewriting the Windows operating system in Java. This one person team won't benefit from more programmers? Of course the project will be completed faster, in this case, with more manpower.
It always results in a period of reduced progress due to drag on the existing staff to onboard the new staff; and the bigger the scale up, the longer that period where you are behind where you would have been without it is. And the more you scale up, the more you need to reorganize and build new coordination infrastructure to make use of new resources even once they are up to speed technically, which also takes time to set up and time to acclimate staff to the new organization and teams, which creates its own drag.
In realistic scenarios, this pretty invariably means late project + more resources = later projects.
But, sure, there are extreme situations where that wouldn't be true, but I don't think they pop up often in practice. One should be extraordinarily skeptical of any claim (or interior intuition) that the rule doesn't apply to your project.