My takes: 1. The existence of “rubber duck debugging”, and a whole bunch of studies on verbally explaining a concept indicate that language is essential for thought. In rubber duck debugging, programmers tell their problem to an object and this is beneficial in finding the solution. There are studies that show when we verbally teach material to someone we remember it better. Also the act of taking a test increases le…
tldr; Language is not required for thought, but on page 3 of the link, "Instead, these tasks engage other brain areas that are non-overlapping with the language network (Fig. 1b), although they sometimes lie in close proximity to the language areas"
I used to do rubber duck debugging, but instead i turned into listing exact step-by-step instructions in inline comments. It seems to work like rubber duck debugging, and all it took was for me to "Externalize the steps" so i can think about what needs to happen at each level of the thought heirarchy.
and section 2. you describe memory and thought as similiar in nature but those are handled in two entirely different regions of the brain.