It can't be done. Behat scenarios are independent on purpose. Otherwise, you would risk state leaking from one scenario to another.
You're not approaching the problem from the right direction. Sacrificing scenario separation for speed improvements will hurt you in the long run.
Assuming that logging in is tested as one of the features, in other scenario where logging in is required, you don't have to be using the actual login form. Think of doing it programaticaly.
Also, you seem to be using Behat for functional testing, while it's build for verifying business expectations. You could consider using Mink directly, which would give you more power.