My two cents:
I actually find this thread interesting and have learned a lot from it. The problem (in a nutshell) is an inaccurate sensor and subsequently inaccurate map. Judging from the Tuneboy data, the problem is especially egregious with the early models, like ours. Not as much with the later models. So, a person may address the inaccuracies on a later model only to have their solution cause bigger problems for someone with an earlier one, which is what I think happened (a lot of the conflict here likely stems from this). What’s good for the goose is not necessarily good for the other goose.
So, I applaud RH’s quest for a more accurate sensor. It makes sense to me. That still leaves the ECU. If he also comes up with a method of re-mapping the ECU (good luck with that) he will be hero of the beach as far as I’m concerned. In the meantime, we’re still stuck with the same mapping problem. Thus, for now, a (perhaps slightly) more accurate sensor arrangement (brass and goo) and a good Powercommander map works very well; perhaps RH's sensor holder and a PC map would work even better. I've already paid for the other solution so I'm not going to worry about it right now. This thread has been very helpful in fine-tuning the low rpm range of my custom map, so, thanks RH. Jason at MI recently said that my bike was the best running V11 he’s ridden.
In any case, I think RH should keep at it. I also think he wouldn’t experience nearly so much resistance if he didn’t precede much of what he writes with a diatribe on what a genius he is and how stupid everybody else is.