Extra Documentation needed + v6.0 Error compilation

I was trying to find many answers to questions I have but the wiki is poor with information and many are outdated. Searching google didn't come up with results I want as well.
I have some questions I hope someone can answer and thanks in advanced.

1- What's the difference between hash mode 22000 and 2500, which on is faster/better?
2- How can I tell hcxdumptool to dump either 22000 or 2500?
3- Is it ok if I do --force for 
Intel's OpenCL runtime (GPU only) is currently broken.
We are waiting for updated OpenCL drivers from Intel.
You can use --force to override, but do not report related errors.

4- I Also updated hashcat today to v6.0.0 and I'm get the following error which I didn't get using v5.1.0:

hashcat (v6.0.0) starting...

* Device #1: CUDA SDK Toolkit installation NOT detected.
            CUDA SDK Toolkit installation required for proper device support and utilization
            Falling back to OpenCL Runtime

* Device #1: This hardware has outdated CUDA compute capability (3.0).
            For modern OpenCL performance, upgrade to hardware that supports
            CUDA compute capability version 5.0 (Maxwell) or higher.
* Device #1: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL API (OpenCL 1.2 CUDA 10.1.131) - Platform #1 [NVIDIA Corporation]
* Device #1: GeForce GT 640M LE, 1920/2048 MB (512 MB allocatable), 2MCU

OpenCL API (OpenCL 1.2 ) - Platform #2 [Intel(R) Corporation]
* Device #2: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz, 8007/8071 MB (2017 MB allocatable), 8MCU
* Device #3: Intel(R) HD Graphics 4000, 1336/1400 MB (350 MB allocatable), 16MCU

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Counting lines in pmkid_Pikskey1304_24-F5-A2-11-EA-A6_2020-04-27T02-14-22.16800...
Counted lines in pmkid_Pikskey1304_24-F5-A2-11-EA-A6_2020-04-27T02-14-22.16800...
Parsed Hashes: 1/1 (100.00%)
Parsed Hashes: 1/1 (100.00%)
Sorting hashes...
Sorted hashes...
Removing duplicate hashes...
Removed duplicate hashes...
Sorting salts...
Sorted salts...
Comparing hashes with potfile entries...
Compared hashes with potfile entries...
Generating bitmap tables...
Generated bitmap tables...
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

Initializing device kernels and memory...
Initializing backend runtime for device #1...
Initialized backend runtime for device #1...
Initializing backend runtime for device #2...Compilation started
In file included from :10:
OpenCL\inc_common.cl:1333:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1334:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1335:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1336:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1337:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1338:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1339:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1340:24: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1387:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1388:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1389:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1390:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1391:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1392:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1393:19: error: 'long long' type is invalid in OpenCL
OpenCL\inc_common.cl:1394:19: error: 'long long' type is invalid in OpenCL
Compilation failed

Started: Fri Jul 03 16:34:21 2020
Stopped: Fri Jul 03 16:34:24 2020
This breakdown will give you some answers.

1. Your hardware is dates
2. Your using a mobile videocard which is not recommended for hashcracking.
3. Hashcat requires OpenCL 1.2 or higher & CUDA SDK for videocards in hashcat 6.0 which appears yours does not support.

As for your questions.
1. Difference between hashmode 22000 is the newer most reliable method for WPA2 where as 2500 is the old standard hccapx which is no longer used.
2.Download the most recent hcxtools and use hcxpcapngtool to convert your captures to the new format.
3. Using force will only cause more grief for troubleshooting as well as possibly cause faulty functionality of hashcat (not cracking known passwords for example)

In short, your hardware is too old for the newest rendition of hashcat.
Thanks a lot for your reply.
Okay no problem I understand my hardware is outdated, I will be using some cloud services.
Regarding question 1, I know 22000 is a newer method, but what is new about it? Does it help cracking faster? How is it technically different?
Can I use the current PMKID file I have to convert from 16800 to 22000? hcxpcapngtool seems to support only cap files as input.

hcxpcapngtool <options>
hcxpcapngtool <options> input.pcapng
hcxpcapngtool <options> *.pcapng
hcxpcapngtool <options> *.pcap
hcxpcapngtool <options> *.cap
hcxpcapngtool <options> *.*

Thanks again for your help!
I forgot to ask you, do I need a handshake or PMKID or both for 22000? Thanks.