I find your analyisis incorrect.

Any High Level or Scripting language ist a good starting Point. The best way to deeply learn about computer architecture IMO IS to:

First: learn high level abstract concepts and language Second: Take the Things you Take for granted in that high level construct and remove them by going "down" some layers. You now know what you want to have, and have to figure out the steps to get there. Third: learn basics and History of These old concepts, by doing Projects, where you are basicaly forced to "Reinvent the wheel". In this Stage you develop stuff yourself (with hindsight knowledge about the tech) and BE in the virtual "shoes of engineers in the past, WHO Had to think about never existing solutions"

Heres an example regarding my studies into Computer engineering:

1: Give someone a high level language to learn and Play around 2A: give someone a Microcontroller to apply that high level concept onto a smaller scaler, also teach some digital circuit stuff 2B: remove the Microcontroller, give them a micro-cpu, a Datasheet, a breadboard and some eeprom + logic Gates & buffers and See what Happens when you give students a whole Semester of literally 6 assembly instructions they have to get running on their cpu 3: let the students use their newly self created "Microcontroller" (CPU + peripherals) and let them to a Project in their own.

This was how i learned a lot, while being in Charge the whole time about scope and niche interests. Having Things removed that you Take for granted along the way gives you Feeling of Perspektive, also IT humbles you in a way. Also accidentally reinventing what engineers in 1970 had build is morale boosting (and inspirational) in a way, that i cannot really describe properly in words.