To put it in simple words - profiler can calibrate parameters that are available via OSD controls. So there's no full hardware calibration possible - it can't put TRC calibration curves in internal LUT of the display. It only automatically changes parameters like brightness, (so called) contrast, RGB gain, but then uses the LUT of the graphics card to correct differences between the resulted TRC and the calibration target TRC (like gamma 2.2 etc.).
You need a display with hardware calibration support and specialized software (like NEC Spectraview II/Profiler or EIZO ColorNavigator) to use internal high bit LUT rather than graphics card LUT.
There's also another issue. It's not a bug, but rather an implementation flaw. i1Profiler does absolutely no tests to see if it can successfully communicate with a monitor. My HP LP3065 has DDC/ci but nothing on the market can talk to it because HP has their own proprietary implementation. Color Eyes Display Pro correctly recognizes that it can't communicate successfully with that monitor and then falls back to manual calibration of the monitor. This is what i1Profiler should do. It should send a command to turn the luminance all the way up, measure that result, and then all the way down and measure that result. If no significant change is measured it should throw an exception and fall back to manual adjustment of luminance.
So that's what it should do. What it actually does is nothing. After it fails to change the luminance via the backlight, it promptly begins profiling the monitor and in order to meet the luminance target, it will remap an output of 255,255,255 to say, 180,180,180 and this is not a good thing.
Cheers, Joe