Excellent, then we can be friends! If you think that cutting power or restarting the CPU is a good use of an operating system and of the computer it runs on, then we're both better off if you wouldn't use the system that I would want to build.
This is very similar to a car. Today it is perfectly possible for the user of a car to accelerate to high speed, and then point the steering wheel at a concrete wall, causing impact. As the implementor of a car, there has traditionally been little I could do to prevent that use. Actually, modern cars with self-driving and safety assist features are trying to prevent that, both by warning the user, and by overriding their decisions (like automatically applying brakes). But it needs to be made clear to the user that deliberately slamming into a wall is not a good use of the car, and will have negative consequences.
Now, this does not imply that we can be sloppy when designing cars: they still need to be as safe against impact as reasonable possible (within the constraint that everything about design and engineering is a compromise with other goals). Because even though we do not wish people to drive into concrete walls (or crash their CPUs), it will happen occasionally, and we need to minimize the bad consequences. And in rare and special circumstances, we need to allow cars to deliberately crash into walls, for example when being tested by the federal department of transportation to determine whether they are crash-worthy. Similarly, it has to be possible to inject faults (such as a CPU reset), for example during software QA testing, and customer's acceptance testing. But we need to make it clear to users that using a hard CPU reset has to remain the rare exception, only suitable for special scenarios such as fault injection during QA testing, and that the correct way to get the machine to reboot is to do a clean shutdown.