Issue with static route with distance metric of 255

Not so much a problem as it is an observation. Has anyone had a problem creating a static route with a distance metric of 255 being inserted into the routing table? Does anyone know why a static route with a distance metric of 255 might not be placed in the routing table?

It has been a while and I do not remember the details clearly but there was a situation in which we wanted to run a dynamic routing protocol with a router (which we did not control) and we wanted it to receive and process our updates but we did not want to put its routes into our routing table. Of the several alternatives that we considered the optimum choice was to set the Administrative Distance of the routes received from that neighbor to 255 which prevented them from being inserted into our routing table.

And the AD that is used by dynamic routing protocols is the same AD used for floating static routes.

One technical nit: an AD of 255 does not make the network unreachable. It makes the route not trustworthy enough to be inserted into the routing table.