I don’t really understand what you wanted to say with your post. I’m a 2 button navigation user and I was having issues. If I’m not mistaken I was the first to report this issue here.
But to clarify my stances as far as I know /e/ OS is based on Lineage OS (which yeah it’s based on AOSP).
I guess the problem with the 2 button functionality is strictly related to the bliss Launcher as on the Lineage OS there is no problem at all (at least for the 2 phones that I have running it). And that’s why I was saying that in Lineage OS it’s working… I wasn’t bragging or making fun of others… on the contrary.
Sure Murena can do whatever they please with the /e/ OS and Bliss Launcher but the excuse that AOSP is dropping support for it is a bit slim since they are not based directly on AOSP(maybe I’m wrong ?!).
Then again it could be hard to program it in bliss launcher, although once done I don’t thick it should be modified afterwards. It was working just fine in the previous bliss launcher so I don’t know where from this problems are arising.
Maybe the number of people using 2 button navigation is really small so they don’t want to allocate resources for it.
Anyway me and (probably) many others could live with the 3 button interface (not that we HAVE to).
There are other areas much more critical where /e/ OS should focus (like multiple camera support).
Just to re-iterate the 2 button navigation is working decently in v2.1 for the S9+ (and probably for others too) on Android T so it might get to perfect in the next OTAs.
Good luck!