There is
nothing to be fixed
As long as Simple x264 Launcher is passing the "correct" CRF value to x264.exe on the command-line – and your confirmed yourself that it
does – there is
no problem on the Simple x264 Launcher side. The CRF value in the job list is
irrelevant.
Furthermore: As far as I can tell, there is
no problem on the x264 side either. As explained before, CRF mode does
not guarantee that a CRF value of
x will result in an
average QP of
x. CRF mode does
not even guarantee that a CRF value of
x will result in an
average QP close to
x. This
may be the case for a specific set of "reference" source clips, but it is
not guaranteed for
all source clips. For your specific source clip it may
not be the case at all!
It was a completely arbitrary decision of the x264 developers to make CRF values live on the same scale as QP values! This is just for convenience. They could have decided to make the CRF value live on a
0.0 to
1.0 scale just as well...
(If you still think x264 is doing anything wrong here, you have to bother the x264 developers. But you will probably get the same answer)