That's like saying an electrical engineer is just a fancy name for a PCB designer. A mechanical engineer is just a fancy name for someone that uses solid works. An optics engineer is just a fancy name for someone who plays with light simulators.
You can't just trivialize what people are doing and then call it not engineering.
The problem with the programming profession is that it's possible to get away with not applying good engineering principles. It's only in domains like the nuclear industry, or the military (fighter planes etc.) where we can really imagine the consequences of buggy software.
Software Engineer is a title that reminds of how we should be approaching the programming problem.
Aka the most junior of juniors? Let's not pretend that will actually produce a working code meeting any real requirements.