1) Yes. And that is where my "fixes" come into play. ;)

2) On a few occasions, I have had to turn VNAV OFF to get low enough to capture the Glideslope, but I never use FLCH, only VS (my preference).
Are you using ActiveSky Next? I had to turn the turbulence right down to prevent it from throwing my payware addons with complex systems (i.e. FMC) all over the place during all phases of the flight. But even with a strong crosswind, one time it was 63knots (well above the 767's limit), it still held the ILS and Glideslope, and landed very close to the centreline of the runway. I just wanted to see how it would perform in that strong crosswind. The wind changed to a headwind of about 20 knots approximately 100 feet above the runway. So even that didn't throw it off it's alignment. Also. Coming into Melbourne, when using Orbx - AU YMML v2 (note that I also have ORBX -AU YMEN, AU YMAV and AU YMMB, which are all in close proximity to YMML), I have had the framerates drop as low as 8fps, but that doesn't prevent the 767 (or 757) from holding the ILS and Glideslope.

3) The ToolTip on the Stab Trim Indicator does match the actual position of the white bar against the numbers, so don't use the ToolTip as the guide, use the white bar and numbers. For taking off in the CS 767, I never move it from it's default position (4.00), and it's climb performance is fine. But I also always use 30% for the CG setting. In the latest version of the CS 757 (v4.6), I do set the Stab Trim Indicator to the recommended setting shown on the TAKEOFF REF page in the FMC, but again, I always use 30% for the CG setting!

4) I agree. It would be great if the mouse wheel worked in both direction and it didn't runaway on you, but thy are easy to stop, just right or left mouse click on them. And it would also be nice if the Altitude Indicator moved a bit faster than it does. ;D