Yes, and doing that still takes time. Murder trials take years and significant human time. Even parking tickets require several people to show up in a physical location to address if you contest them.
So, you either do the proper, constitutionally required procedure - which takes time - or you take the Nazi approach of... significant shortcuts. And even there, it remains quite labor intensive.
And now, oops… lettuce is $20/head, and the international community is working to send you to The Hague.
If the system is overloaded to the point a border trial takes years then there needs to be more investment into the resources needed to speed up the process. Making things slow and inefficient is not an inherent thing that needs to be preserved. This is why original comment suggested scaling up enforcement due to deal with the increased load of essentially clearing out the queue of current things that need to be taken care of as opposed to spreading it out over time.
> Making things slow and inefficient is not an inherent thing that needs to be preserved.
The opposite, really. Making it slow and inefficient is how we try to prevent life-changing mistakes like "oops we deported a citizen and now they're dead in Tijuana".
I would actually expect the opposite. The slower and more inefficient a system is, the higher probability a life changing mistake happens. The more frequent something happens the better a system gets at handling that thing.
Take for example restoring a site from backups. If you never have exercised disaster recovery before you may make some mistake or realize that something that should be backed up isn't. But if you practice disaster recovery quarterly you are much more likely to discover these issues.
