I'm not sure you could get anything from listening to a codebase that way. When I'm programming, I often move line by line, so I can stop an think about particularly complex sections. Or sometimes I move character by character, in the case of deeply nested if statements. Plus, my windows screen reader has methods to tell me how deeply indented I am, so I can track scope etc. I often skip from one level to the next, so I can skip over blocks of similar or uninteresting code, rather than have to listen to it repeated over and over. When I'm "listening" to code, I never just start it reading and sit back and listen. It's a deeply interactive process, involving lots of skipping around, lots of changing granularity (from character to line to code block etc), and sometimes even adding explanatory comments to parts of the code I know I'm going to forget, and don't want to have to listen to entirely multiple times ("// Standard network initialization; next section does nothing interesting").

TalkBack is one of the most limited screen readers and as far as I know, still does not have the option to read punctuation. You are better off using a desktop and NVDA, which lets you bind a key to do exactly what you're asking.