But none of that is meaningful work. It's shuffling the deck chairs. No matter how efficient, it won't do anything about the ship sinking.
None of these facilities solve actual problems. How does any of these features help me better align the UX experience with target demographic? How does it help reduce turnaround time on reporting? How does it ensure better culture fit across different stakeholders? How do they help me reduce failure rates in deployed software? How do they help me choose most suitable architecture trade-offs given requirements?
All these features do is they help move text around faster. But they don't help with any important problems in a way that choice of better ecosystem would. The "solutions" mentioned above are endemic to Java and .Net which are just absurdly verbose for the trivial and mundane tasks they are solving.
What's your point, exactly? No one is arguing that using an IDE writes good code for you.
The question at hand is whether using an IDE has any benefit over not using an IDE. Doing the same work but making it faster, easier, and less error prone may only be "shuffling the deck chairs", but isn't it still a benefit? Doing the same work but in less time is an obvious benefit.
My bike can get me anywhere my car can. Does a car then have no benefit over a bike?