Let's turn things around to look at them the other way: Is it worthwhile to do the BDD process without BDD automation? Again, it's a compromise that's better than nothing.
Does it make sense to use a BDD test automation framework when the team does not follow a BDD process? Yes! It's not an ideal situation, but it still has good reasons.
Should code reviews be rejected if the code contains typos? While this rule may seem controversial, I say YES for 5 main reasons.
I recently learned who "The Three Amigos" are, even though I always practiced the mindset. This post explains how to bring 'em into BDD.