Uh... why? It's a configuration option. It's not impossible to do afterwards,
and if implemented would limit the usefulness of loop detections in the first
place. A special case for use often needs a little configuration.

Um, please remember I'm just the messanger here.
Because thin clients have different needs, and, particularly in
the case of k12ltsp, removing some of the deeper darker
configuration voo-doo is gonna be neccessary.
Please feel free to suggest a better number than 250 if you wish.
However, understand that the number was arrived at with
Real World PXE booting experience, something we are sorely
lacking in at the moment.

The loop detection in 2.3.3 and earlier is clumsy, and duplicates some of the
functionality in the configuration section. It's clumsy because the -loop
option is passed on the command line and can't be overridden in the config
file.
The current development branch of xinetd removed the -loop option, since the
per-service 'cps' directive (connections per second) duplicated much of the
purpose of -loop, but is more configurable. It still defaults to on, with the
old compiled defaults, but is at least configurable now.