SInce it's static analysis based probably you'd remove less obvious code that uses macroexpand, eval, other tricks.

That's a risk, yes

Perhaps having a (commonly known?) way to run (unit) tests against your uberjar could help mitigate some of that

You can just pass the target directory as class path after running carve, before uberjaring