Is there such a thing as being overly cautious? How do you balance certainty with velocity?

Where I work, we have a lot of bureaucracy when it comes to things like testing criteria, code reviews, meetings, deployments, etc. My manager is also a by-the-books kinda guy, and it's rare for him to be flexible on something.

For example, even if a change is small in scope and low-risk, he won't let that pass without a code review meeting with the team. And convincing him that we tested our changes thoroughly enough can be challenging, as he seems apprehensive to any risk, especially if it involves touching an already written part of the code.

New deployments that have never been done before need to be setup through an internal tool, which requires sending a ticket to a different team to do. Even in testing environments.

Standups range from half an hour to an hour because of post-standup discussions, but most of the time, the manager's talking with individuals one-on-one, rather than full participation by everyone.

I'm sure the need for these processes is based on past experiences that I'm not aware of. But I'm a calculated risk-taker. As in I'm constantly doing the whole "speed - chance of failure * cost of failure" in my head for any task, and it seems my "chance of failure" estimate is always less than my manager's.

I feel like I should be able to make changes in a shared testing environment quickly to iterate on theories (obviously there should be guards against modifying critical files or files owned by others). I've had my fair share of issues that I couldn't reproduce locally, but could reproduce in said shared environment, and I can imagine how much time I would've saved if I could iterate quickly.

It's hard to follow meeting discussions that aren't related to my work because I don't have enough knowledge to follow along, and interrupting the flow of these discussions so they can catch me up would probably be less efficient than if I did my own research when said work actually becomes relevant to me.

Am I looking at this all wrong? If so, how can I better understand the other side to this? If not, how do I cope in this environment, because it gets frustrating at times and throws off my estimates.