Yes, it would be possible to implement some additional verification mechanisms of the masternode configuration into the program, but after reading the discussion, I begin to conclude that it would not be the best approach. The point is, that the Dash functionalities planned for the coming months will require masternode to provide much greater availability/QoS than it was before. This in turn will face the mn operators to deal with problems that could have been ignored until now, which will require some technical knowledge about the operating system running the Dash daemon and a lot of knowledge about the specifics of the Dash network. People without such knowledge trying to administer masternode sooner or later will get into trouble. For such people, it is probably better to outsource this task to professional vendors (operators). Here I do not mean people who want to learn it, because almost everyone can do it. I mean people who do not want to (because it is beyond their interest) or simply do not have time for it.