Radial deadzone is the most common, it is a circle around the center to adjust for centering calibration.
Axial runs the length of the axis at the assigned deadzone width. But this also should keep the cursor from drifting, so it must not be working properly(or broken sensitivity was the cause). This type would not be desired for player or camera movement as there would be a dead spot when crossing the axis.
I did notice the cursor drift moving the left stick with your profiles, but stopped doing it when changed right to radial(but also changed the sensitivity settings). Maybe there is some bad code in the axis tuning mixing the sticks up. Could be the sensitivity doing it as we know that is broken. So I would try leaving the sensitivity at default as all it does anyway by lowering it's value is crop the high output values. So the full movement outputs less than full value but spreads the lower values through full movement. Down side to this is you won't be able to achieve the faster speeds of the higher values. This is when a sensitivity macro toggle would be handy, but not much use when it's broken.
I don't see him fixing any of this as he is needing all his available time in getting 1.7 out. Which essentially is the fix for all this.
If you haven't already you should check out his latest check-in video which covers his plans for mapping and axis tuning.
Asus STRIX X299-E GAMING MB, i7-7820X 3.6/4.5GHz 8-Core, 32GB Corsair Dominator Platinum (CMD16GX4M2B2400C10), NVIDIA TITAN X (Pascal), Samsung 970 Pro 1TB M.2-NVMe w/Western Digital 2TB (WD2000F9YZ), Samsung 65Q9FN QLED, HTC Vive, 850w PS, W10