In our previous iteration of our startup. We were trying to build day2 infrastructure automation platform. Based on interview with customers, engineerings, managers and first version of the product, we arrived at the conclusion that it is close to impossible productize because of the exact the reason the commentor is mentioning. Starter workflow or templates sounds like a good idea but in reality minor tweaks need to make it work will push you to make significant investment to learning them.

In real world, permutation and combination are endless. Every org has peculiar problem either created by the engineers themselves or are result of certain business decisions.

I'm imagining something similar to a 3D wireframe model of networks and systems, with particles that move around between nodes that represent requests or IOPS.

Circuit breakers, bottlenecks, IOPs, load shedding, traffic behaviours can all be visualised.

I'm not sure how you would represent latency with this visualization but that's also important. It more represents throughput.

Can also be used to represent human work/tasks itself.

Sounds a bit complex, I usually stick to the R.E.D. method for services and from the devops perspective largely iteration speed.

Well you could use some heatmap to represent latency, where the hottest part would be those of high latency, turn those particles and boxes red or blue depending on their mean latency...