I am sot sure I understand what you are saying... The probe should stop immediately (depending on how fast you are probing, since it has to decelerate the motion and stop in a controlled manner) when touching the material, after that it will move back (retract) the probe and make a new probing at slower speed to remove the slight error may have been caused by the first, faster probing. After the second probing the probe will be retracted to a preset distance from the probed surface and stop. This is the way it works for every type of probing. If the probe is pushed into the stock then either it is configured wrong or you have some sort of other problem with the installation. Dave had several issues related to his way of testing, the installation and the configuration perhaps also the probe used. I never really got answers to my questions, so I don't know how it ended, but I know that the probing is NOT pushing the probe into the stock if everything is set up according to my manual and the machine is built and configured right.
So, if you have issues you should describe the issues you have and maybe I or somebody else can help you. The probe radius should be set to zero ONLY when the radius is not important and you are not looking for the centre point of the spindle as zero point, but the edge of the probe. This is OK in some cases but will cause problems in other, so it is NOT a universal solution to every problem.
So please explain what sort of problems you have because to me it is not clear. I assume you read the manual and using the last version, and also using the official release of UCCNC, not one of the test releases. I don't know if test releases have issues or not, and it is not recommended to use any test release for production or when errors can cause financial or machine issues. I know that 1.2103 had serious issues and was pulled back, but the latest official release is working. I don't test the probe with every release, I simply have no time for that and my probe screen is a free product, so it is up to the user to test it and make sure it works after every change. I try to keep my machine up to date, but never roll back releases unless I see some issues which are not acceptable for me. Unfortunately I can't test with every release and can't even guarantee to install every official release, let alone test releases.