MultiSphere Trace not returning Impact location

See my answer to the post. This is not a bug; in the case of initial overlaps there is no defined ImpactPoint or Location. 4.8 will make this more clear in the exposed values in BreakHitResult and in documentation.