The exception from your screenshot will happen if you are traveling in the negative direction and the positive switch triggers or vise versa. This could potentially arise from the noisy input previously discussed.
If you are using a longer trigger duration for the switch and a slower homing speed would be recommended to accommodate for the slower switch reaction time.
After a bit of investigation, I’ve come to the same conclusion as you. Homing deceleration is effectively not used the way our master based homing is currently implemented. I will update the documentation accordingly. The only situation it would be used is if the maximum homing travel is exceeded and a switch is never hit.
If you want to change the deceleration of a master based homing method you can use StopTimeSet()
If our master based homing methods are not working for you I’d recommend creating your own homing routine. They are fairly simple to implement. And being able to debug the code directly could save you a lot of time.