I'm doing Sat Autoscan for 118.7W, while LNB is switched OFF in the receiver for 119W. Otherwise Autoscan produces many 119W channels, and Blind Scan produces a number of duplicated 119W channels on both 118.7W and 119W sat channel lists. I tested 11870 freq at 2000 V 7/8, and it gave a list of Echo 7 channels, when scanning this TP for 118.7W sat, while LNB is OFF for 119W sat. It looks like you're right on this one.
Let me try this another way.
If you set your LO to 11250 while using the circular port, it is scanning 12200-12700.
If you set your LO to 10750 while using the circular port, it is scanning 12200-12700.
Ie, with a standard lnbf, the band that your receiver sees has nothing to do with what you set your LO freq as. That setting is only used to convert the 950-1450 IF band into a freq that is displayed or used to select an IF freq to tune.
I'm still a bit confused about the receiver setup, particularly when you say things like you've turned off one sat or the other. It sounds like your receiver has some special setup that is intended to handle a Dishnet lnbf setup, of which there are so many types, I've given up trying to remember what they all do. If that's the case, you shouldn't be using a setup like that for a QPH-031. You should set up that lnbf as a standard or single lnbf, regardless of whether you're setting up the circular or linear port. If you're setting up a sat for the linear port, you use 10750 LO freq. If you're setting up a sat for the circular port, you should use 11250. Using 10750 while using the circular port will do nothing except give you some channels that appear to be at the wrong frequency, or in your case, will appear to be from the wrong satellite.
When you say, the receiver is tuning to 1120 for NASA channel - could you elaborate on this?
Your receiver does not receive in either the 11700-12200 band or in the 12200-12700 band. Your receiver receives in the 950-1450 band, or actually it goes past that, ie probably from 950- somewhere around 2000. This is because you're using an LNB which is a block down converter, ie it converts the Ku frequencies down to a common 950-1450 band whether you're using a Ku or C-band lnb. So when you think you're tuning say the 12370 freq on your receiver, you're actually tuning 1120, which is 12370-11250. The Ku frequencies that your receiver uses are only for display purposes, and for doing the conversion between L-band and the actual frequency being received by the lnbf.
Some people, using some receivers don't even use the C-band or Ku-band frequencies at all, and perhaps that would avoid a lot of confusion. For example, DCII receivers use the actual frequency that it's receiving in the 950-1450 band. My DCII receiver has 2 ports, one for C and Ku, but I never use my Ku band port. I just put Ku into the C-band port, because it doesn't matter, because it expects 950-1450 on either port, and that's what I input when I tune it.
Many people do the same thing with some DVB FTA receivers too. Ie they just set it up with a LO freq of ZERO. Then if you enter the actual IF freq, you'll tune the same channel. I don't know if your receiver will accept a LO freq of zero, but if it does, you might try that. Ie use LO=0 and set up a transponder with freq=1120V SR=20000 . You'll probably get the same NASA channel when you do a scan.
As to Lyngsat, a lot of TP and Channel info is obsolete, but some of what people perceive obsolete may be caused by regional TP spot beam related differences - don't you think so?
Yeah, sometimes people can't see transponders, and report that they aren't there. But relative to obsolete, it's probably just more a case of people are more likely to report a signal if it is new than they are when it goes away, so things tend to stay in Lyngsat long after they have gone away.
That aspect doesn't bother me so much, as I just look at the date, and anything that doesn't have a current date on it, I don't trust.
Also, there are a lot of innacurate frequencies and SR values that are on Lyngsat because some receivers report the wrong values on blind scans. The Mercury II is notorious for giving the wrong values. I think MY Mercury II would be off by enough that a couple of my other receivers would not be able to lock the transponders about 95% of the time.
However, the third issue is information on Lyngsat that almost HAD to have been put in there intentionally with incorrect info meant to confuse people. I don't know why people would do this.
The receiver doesn't tune either 11870 or 12370, for the NASA channel, it's tuning 1120, and it's basically telling you that the frequency is 1120 plus whatever freq you tell it the LO freq is. 
