This is answer for specific OP's circumstances: beginner working alone. For a beginner working in a big team, advice would be "follow your leader". YMMV, and you are free to do whatever you want with your own time.
In general, experience in more generic tools ("clean" Selenium) is easier to transfer to other positions, easier to grow your career in the future.
I suggest to continue using Selenium, learning about design patterns and refactoring. Then, you might realize that what you are developing is BDD (or that BDD does not make sense for your specific setup).
Also, one good rule of thumb is: "If it isn't broken, don't fix it".
It is good sign that you are concerned about using best practices, but build basic skills before you are making long-term decision.
I do not believe that promise of "business person reading your tests in BDD" will work. Those are empty promises, AFAICT. I have personal experience with a tool making similar promises FitNesse and it was a failure. Using "clean" Selenium gives you full power of your programming language of choice (so you are gaining relevant transferable skills), BDD forces you to work in way they designed it for you.
You can always try for a week or two and see if it fits your need.