Well, taking your example, I don't think it would need an such an "extra protection". I wouldn't like to be forced to read that information when I don't need/want it. I'd rather read a good warning in its section of the help file so I should only use the command when I know exactly what I'm doing and can realize the consequences. If anything goes wrong, I should know it might be the /ialset; use /ialclear and the issue is gone.
Like with /fopen. The help file says you should always /fclose your opened files after they have been used to make them available to other applications. Also, you should check $ferr, $feof etc. yourself. If you don't understand how to use them, you're clearly warned not to use them. Yet, you don't see any /.f* command (and related identifiers) displaying anything by force, unless an usage error (like /fopening the same name twice) occurs.
IMO, /ialset could follow this behaviour, then it should be fine.
