Yes, it can be a long-term career. You need to think about what you like doing though because Salesforce often brings you in contact with a different set of customers. You will need to develop consulting skills which you might not have over the long-term. These are the things that will give you most longevity.
Consulting is a blanket term I'm using for what is in many ways a jack-of-all-trades. These are seen by techies as a negative in many careers, but is a life-saver if you go the path of Salesforce. These include: analyzing proposals, communication with non-technical people, analyzing existing systems, change management, and influence without authority.
You need to start at the bottom and ideally get to work on some larger Salesforce deployments where you have limited responsibility. That'll give you space to learn with lower risk. You'll get to see some of these consulting skills in action over a few engagements if working with reasonable companies (do a lot of research on how companies treat IT folks.) This will help you adjust because the life of a great Saleforce dev involves engagement outside of IT.
If you don't have interest in developing these consulting skills then Salesforce will start to feel like CRUD web dev again. The skills open up opportunities to do more interesting things, or be involved in design of the systems, use newer Salesforce products, etc.
It's interesting that you complain about CRUD because 99% of web dev is CRUD when you look at all web dev. There are small group of devs who are working on startups, open source libraries, or unusual areas of web dev. Most people are just building business apps or sites that read and write data. Moving to modern frontend dev and the like is justified for various reasons among regular devs, but most often everyone really just wants the novelty after years of server-side CRUD. Nothing wrong with that, but we could be more honest and less defensive about it.