Jay, you are 100% correct and that is what I tried to convey early in this, that you can do anything if willing to manage sensor input in open or closed loop when appropriate if the system allows. However it is not just a cheap system that can trick an O2, it is ALL systems if you use that sensor in a closed loop option, the question is, does the system have the ability to allow you to tune around it and will the vehicle behave the way you want it to when you do?
Anyone who tunes seriously uses the open loop regularly when needed, but it is limiting the function of the system by design, and to be honest, using a purely open loop speed density system will run great, but is limited in it's ability to adapt if you have an engine that doesn't need to run open loop.
Let me qualify what you said too, because I actually run a more "real" system than a FAST SD by running a MAF system with both WBO2 and NBO2 and left and right bank inputs. The modified OEM system I use is more adaptable than any speed density system because it additionally measures intake airflow, something a speed density system cannot do. The system is also modified to only adjust a/f tables using WBO2 in those times that I allow to and uses NB for normal operations. That NBO2 is limiting in itself in its narrow range of responsiveness, and I may actually dump them now with a recent upgrade to the software, but having the input for both styles and the combination of logs that can be combined with load, speed, airflow, ambient temp and pressure, etc, really works well.
In the end though, open loop is not as responsive by design as closed loop and depending on the use of the car, may not be as happy as yours have proven to be for your use. It is essentially creating a map or table for a given range as you discuss, if you want a multi-dimensional map and want the system to adapt it, that O2 sensor is a very good thing (until you have a characteristic of the engine or environment that you cannot do it, but on a pure streeter, IMHO the goal should be to get back to closed loop if/when you can)
I do agree with you completely though, when you have a system, and that system has the ability to be manipulated for your use, and you learn how to work it, it becomes very usable.
I am also not a cammer guy, but I am interested in what your equiv overlap at the valve is with a 286@.050 SOHC cam and how they are installed compared to a wedge, my hunch is a quite a bit less duration at the valve with the low rocker ratio so therefore less overlap. (Although I bet the overlap on a hemi does have more authority) Not that it matters with the way you use your system, but if i remember correctly, you mentioned that the cam has to make up rocker losses. Regardless, I cannot see a a 286@.050 being the right cam choice for an EFI wedge with a 2.63 final drive, so hard for me to recommend open loop operation for a 600-ish hp wedge.
For the crowd, you are seeing the most common EFI argument on the net unfold between experienced guys though
technique vs technique. I try to avoid open loop and get into closed loop as often as I can because of the rpm range and power levels I am tuning. Jay is building for MUCH more power and RPM, needs those tools and is experienced to tune to it. Who is right? The answer is yes LOL but bottom line, neither could do what we are doing with a handheld controller
I also need to echo Jay's tuning fun comment, file save, reload, try something new again, sometimes even in a parking lot on the way home, undo and go back to last Thursday's load, all in the course of a ride across town without getting dirty. It's cool as cool can be