The blueprint is at the bottom of the override chain. If you have a blueprint implementation, then that is what gets called first by the framework (it’s called by the generated implementation of the method, the one without the _Implementation suffix, which you don’t define yourself). Calls to Super in your own _Implementation definitions have no effect on that process.
If you were to invoke the method initially by calling the _Implementation, then yep, the blueprint would be skipped. I’m not suggesting that though. So long as you invoke using the base method name, that should dispatch to the last override (be it blueprint or C++), and then you are free to pass on up the chain using the line I gave above. This has always worked as expected for me.