Sam Newman makes a compelling argument about the software architect as the "city planner" in Building Microservices. If not sure if you've borrowed the idea from that book, but if you haven't read it, you should — you'd probably find it interesting.

You make a valid point: designers of building and designers of software systems go about their work in necessarily different ways. But I'd invert the call to action. Rather than "stop applying the term 'architect' to software", I think we need to stop assuming that the word "architect" always denotes a designer of buildings. "Architect" (both the noun and the verb) often applies across industries and endeavors — not just buildings, and not just software.