Release v6.22.2-mo1 no longer benchmarks

[ZeddieXX]

Version in title.

Created a config.json file using this site:
https://xmrig.com/wizard

Normally this MoneroOcean version of xmrig would run an algo benchmark and will create additional values in the config.json that would indicate the CPU's tested performance for each algo.

However, this version does not perform a benchmark anymore. Also, I cannot force it to use a specific algo (I really want to see how well flex will do on this specific machine), but it always reverts to rx/0.

The config.json values that are no longer being created by 6.22.2-mo1:

    "rebench-algo": false,
    "bench-algo-time": 90,
    "algo-min-time": 0,
    "algo-perf": {
        "cn/0": 1138.9523745504655,
        "cn/1": 953.7181399132321,
        "cn/2": 953.7181399132321,
        "cn/r": 953.7181399132321,
        "cn/fast": 1907.4362798264642,
        "cn/half": 1907.4362798264642,
        "cn/xao": 953.7181399132321,
        "cn/rto": 953.7181399132321,
        "cn/rwz": 1271.624186550976,
        "cn/zls": 1271.624186550976,
        "cn/double": 476.85906995661605,
        "cn/ccx": 2277.904749100931,
        "cn-lite/0": 2622.254340117305,
        "cn-lite/1": 2622.254340117305,
        "cn-heavy/xhv": 1445.979329468112,
        "cn-pico": 17836.98026957077,
        "cn-pico/tlo": 17836.98026957077,
        "cn/gpu": 198.47418037607756,
        "rx/0": 10046.904409787578,
        "rx/arq": 46103.747899159665,
        "rx/xeq": 46103.747899159665,
        "rx/graft": 9437.742634825136,
        "rx/sfx": 10046.904409787578,
        "panthera": 11969.330308377448,
        "argon2/chukwav2": 16441.60602342818,
        "kawpow": -1.0,
        "ghostrider": 4193.532146273516,
        "flex": 1710.515263007577
    },

[ZeddieXX]

Also, adding the values back manually seems like this version of xmrig ignores it. For example, setting "rebench-algo"=true, normally will force xmrig to rebenchmark the algos, but this version ignores it and goes straight to live mining using the rx profile.

FYI, reverting back to 6.22.1-mo1, benchmarking behavior returns and seem to respect the values in config.json