I'm just finishing sculpting quite a hefty model in Blender. This way you would not go into the dangerous region by one click, but rather smoothly descent. IMO the optimal soution would be to have logarithmic/nonlinear sliders which would work similar to the brush radius slider in Krita. So for very high resolution the normal remesh feature in the mesh data properties would be always preferred. Keep in mind this is about the modifier version of voxel remesh, and it makes no sense to have an extraordinarily slow modifier in the stack. If the modifier did clamp the voxel size it would give an error message to the user as well indicating that. The modifier would check the bounding box size and make sure that memory usage stays under some reasonable amount. If there shoud be a limit, then that should be calculated at runtime of the modifier. I think that the solution should not be a hard limit of 0.01 in the UI.

A value of 0.001 on the default cube does still work on my computer, but takes very long to compute, but if I scale the cube down in editmode by 0.01, then even the voxelsize of 0.0001 works. Currently there is only a soft limit for the voxel size at 0.0001, but you can also type in something as low as 0.00002.

Krita keeps crashing