I imagine most here have day jobs with projects that last more than a few months so I doubt the need to learn things faster than your cycles of your job.
True, but unless you own the business, the business' goals are not your goals. The business wants a working product; you need to stay relevant in a career. Sometimes these may align, but not always.
When I hire devs, I base their relevancy on what functionality and results they produced for their employer/project, not how new their tech stack was.
Go ahead and learn new stuff but if you know the fundamentals, the frameworks are just different syntaxes for the same thing. But don't assume that someone who doesnt keep up with things every day or week is somehow irrelevant. These frameworks won't change your productivity that much and your output is what matters.
None of the productive developers I know care about all the daily/weekly noise, if something is truly new and good it'll become known on a monthly or quarterly scale.
And about job description - developers are hired to build functionality, not learn new things. It might help further your personal goals and eventually help provide functionality faster/better using new tools but at the end of the day, the business doesn't care and would rather have something that works. Don't get caught up in the hype. It's great that you seem so passionate about it but keep in mind what the work is really about.