Okay, I understand your approach now and agree: There are many ways that developers can change their coding style to either improve performance, or work-around Construct engine limitations on performance.
I think it's still wrong to promise everyone that you can "bring CPU down to 5%!", as a developer might already be using those techniques, at which point there is no magic improvement to be expected.
There's also situations where optimizations like those will not always work, so it's just a "good performance advice" course than a "how to make JavaScript faster than Native C++" course.