You can actually change that value at runtime and see the new clipping parameters take effect. If you wanted to, you could potentially save a float for as many near clip values as you want and change any of the values during an event or in a tick. Then use the console command “r.SetNearClipPlane” to apply it to your active camera (and all other cameras you switch to until you revert the Near Clip back). If you’re using blueprints then you can use the “ExecuteConsoleCommand” node to automate the process for you.
I’m not entirely sure how slow it is to be calling a console command every frame, but certainly it isn’t recommended. If you’re concerned about speed then you can probably find the internal functions being called and avoid the console completely. To be honest though, I use the ExecuteConsoleCommand node a lot and have used it for this exact purpose =P