It is always good to learn the abstraction layer below when creating something. For designing physical objects that will one day be physical products, it makes a lot of sense to understand the manufacturing process and materials involved.
To use your example of software... I've encountered one too many people who are billed as an Enterprise software "architects" who have never coded a single line production software in their life <cringe>. Needless to say, these projects almost always end up a disaster.
I think you misunderstand the purpose of that kind of architect - their job is to wear a suit, give good PowerPoint and disappear in a puff of UML when it comes to actually building software.
I am aware that it is common practice for a guy with a title architect be the "smoke and mirrors" guy during the sales phase.
I am referring to so called architects who have the role of leading a group of programmer during the building of software. Unfortunately many times their understanding of software does not go beyond the Visio and Powerpoints but it is falsely assumed they can still lead due to pointy-hair-boss soft skills. What ends up happening is crapware due to a lack of understanding of fundamental software design and process.
To use your example of software... I've encountered one too many people who are billed as an Enterprise software "architects" who have never coded a single line production software in their life <cringe>. Needless to say, these projects almost always end up a disaster.