Oof... that's going to be a hard pass from me. Everything should be tested, and if you're not going to test something, there had better be a good reason.

Offloading your worries about breaking things to your tests is the entire point! That's a pro, not a con.

Having worked in companies that aren't disciplined about writing tests and also companies that are excellent at testing, the ones who emphasize testing have much cleaner codebases and way fewer bugs.

I'm agreed with you on favoring integration tests over unit tests. Kent Dodds' article on it sums up the reasoning behind that pretty well: https://kentcdodds.com/blog/write-tests