This is why it's so important to do lots of engineering before writing the first line of code on a project. It helps keep you from choosing a tool set or architecture out of preference and keeps you honest about the capabilities you need and how your system should be organized.

I can think of two major ways to operationalize a Python script that needs to run continuously. One is with containerization, which usually means Kubernetes, which already has a perfectly fine resource definition for cronjobs. The other approach is to run the script in a bare metal or VM, which would mean defining a service to ensure that the process can be managed appropriately, restarted if it dies, and the like. In other words, defining a service is about just as much effort as defining a cronjob, and there's no escape from some amount of "ops work" that isn't encapsulated in a Python script.

So why not just use the tried-and-true prior art than worry about building and supporting your own secret third thing that others would need to learn, support, maintain, and keep in mind when debugging a problem?

This is all while companies reap the benefit of and build their pricing structures off of cheap, undocumented labor. We are profiting off of criminalizing people who are just trying to live their lives.

You might count yourself fortunate not to be in this kind of a predicament, but it may benefit you to consider educating yourself on the subject and having a bit of empathy for others instead of relying on categorical absolutes.

Your analogy of an illegally parked car is spurious because where a car may park is pretty unequivocal. I hope that what I've described here helps you understand that this would be like someone choosing not to tow a Ford but opting to to tow a Kia even though they're parked against the same red curb.