One reason calculus is a good prerequisite for CS is that it's typically where you introduced to the concepts of limits and are taught how to look at a formula

One reason calculus is a good prerequisite for CS is that it's typically where you introduced to the concepts of limits and are taught how to look at a formula and see how it behaves at extrema and critical points, if you're good it can be done by eye or with some basic white boarding. And that's (in the broadest strokes) the key skill set for complexity analysis and software architecture. One of the worst trends I've seen in recent years is the dogma of benchmarking and profiling as the gods of performance analysis. Any decent software engineer should be able to reason about how a program behaves by reading it before reaching for automated tooling - which by the way, won't tell you why a benchmark is bad or why some section of the program is a bottleneck.