The use of 'may' to leave for implementation flexibility may (heh) cause confusion. COnsider simpler language which describes the current implementation rather than just the API surface.
We won't need to override this in FNA3D, since we only use hints and don't interact with the CLR anyhow. Fixing it in FNA.dll will cover all the bug scenarios in this case.
Required for https://github.com/FNA-XNA/FNA/pull/437
Discussion
Hint
naming?Set/GetEnvironmentVariable
Override
in the name?