You can put things in a license that are not legally enforceable.
You could add: "All users must sacrifice their first born child to the developer". No court in the world would enforce that license.
This is a contrived example, but what is enforceable will vary in different legal jurisdictions.
Things are not black and white, which is why it is incredibly common for their to be lawsuits disputing the meaning of validity of a license.
This is why it is best to consult a lawyer before changing a license.
It is important to rename a modified license to avoid confusion. If you tell someone your software is MIT licensed, but you modify the license, they might inadvertently break the terms because they are familiar with the MIT license, not your modified license.
There are a lot of open source licenses out their, I strongly suggest finding that suits you best.
Using your own licence might hinder adoption. There some people that don't consider a license open source in unless it is OSI approved. I don't agree, but it is a good idea to stick with OSI approved licenses.