FXAA and Triple Buffering are mutually exclusive in the driver, and I believe FXAA takes precedence if both are enabled, so yes your deduction is correct. This is working as intended.
Agreed, although there doesn’t appear to be any mention of FXAA in the documentation either (README.BZ2 on my system), so perhaps those changes will both be coming in a future release.
Yes, that’s a good point. I’ve filed internal bug 1172418 to track the tooltip update, and we’ll look into what kind of additional documentation is appropriate for FXAA.
Just thought I’d note that FXAA built into a game does not seem to be affected by this. E.g playing Skyrim or Dishonored under wine with built in FXAA doesn’t result in drops to locked 30 FPS. Same goes for the linux native version of Serious Sam 3. I’m guessing that the way the driver forced mode works won’t allow for this to be fixed, but it’s good that games that support FXAA themselves will work without out large performance losses that regular VSync entails.