All I can say: in my experience, the engineers I've hired with deep (but potentially old) experience and with balanced resumes have been better performers and more likely to stick around than those who bounce around tech to tech.
In my experience, it's useful to have a couple 'jack-of-all-trades' types on the team, but you wouldn't want all your engineers to be broad but shallow. I did a stint in the military to pay for college, and something we'd point out was that it was better to have something 'good enough' right now than something perfect a thousand miles away. Breadth of experience is also handy when trying to innovate a novel solution.
But I don't have any better evidence than you. I've never worked anywhere large enough to have that sort of data where we could demonstrate quantitatively that one method works better than another, and of course the metrics are all fairly arbitrary themselves.
If you bring nothing but J2EE 1.4 experience I'm going to assume you've carved out a focused niche. I'll steer the interview towards broad, modern practices and technologies.
If your resume talks about nothing but modern technologies, I'll try to dive deep to be sure you aren't a dilettante with surface knowledge in a ton of things but no deep capabilities where it matters to $company.
In general the best resumes show a balance of deep expertise in foundational tech and exposure to new technologies. A dev might have done Python for a decade but has started poking at Elixir, an ops person knows Linux like the back of their hand before they start talking about Kube, etc.