For programming, querty-typing speed is not really a bottleneck for me. I already don't think as fast as I type.
I would like to be able to take notes as fast as people are talking, though, and for that you do need a chording keyboard.
I don't think that's true. You've probably had moments when you had the entire design of a program in your head, and it required typing out hundreds of lines, or even thousands, all of them mostly conforming to the original idea.
Sometimes, and more so in certain languages and the way they are used, massive amounts of boiler plate are required. Programmers use copy and paste techniques to do this, which are basically devices for massively amplifying typing speed and accuracy. When you copy 50 lines, and then change five places in the copy, that's faster than typing them from scratch. The editing commands are a kind of shorthand, which gets expanded in the editing buffer.
I would argue that for writing code sure, but that programming also includes communicating with other people and writing documentation. In those cases being able to type faster really is an asset. I've worked with multiple older programmers whose typing speed is not up to snuff and they turn anything more than a trivial question into a Teams call just not to type things out.
...but yeah, for actually writing code IntelliSense or whatever just makes it fast enough that if you can touch type at any speed you are not gonna be bottlenecked.