I've had the opposite experience working with a mix of uni-attendees and not.
Compared to their university-attended coworkers, the straight-to-industry folk were far more likely to cargo cult design patterns, languages, and frameworks.
A bit orthogonal to the actual discussion at hand, but I've become a big proponent of cargo-culting in a pragmatic fashion. I definitely ensure that everything is done in the "Rails Way" for any Ruby on Rails code, despite not necessarily agreeing with what's considered the "Rails Way" by rubocop or general rails developer consensus. If I'm doing code review for my colleagues I'll force them to refactor their changes into idiomatic Rails code, even if it's perfectly functional code. I'm less strict on JS or other languages, purely because I lack the experience to say what's the "right" or "wrong" way.
If your codebase follows a well-recognised style and pattern, it becomes a lot easier for new hires or contractors to get on their feet and start productive work than if you have some kind of brilliant idiosyncratic codebase that takes 3 months for a new hire to get their head around (as was the case when I joined my current company).
Compared to their university-attended coworkers, the straight-to-industry folk were far more likely to cargo cult design patterns, languages, and frameworks.