In this case, it is, though, because the security prompt to enable the kext in question doesn't have an "OK" button. It doesn't really offer a button to perform

In this case, it is, though, because the security prompt to enable the kext in question doesn't have an "OK" button. It doesn't really offer a button to perform the action at all. It offers a shortcut to the System Preferences pane where the user would have to unlock the pane, type in their admin password, click on the extensions button, and then click to allow the extension. If the user has jumped through those hoops to enable this, they've already passed the barrier of entry. This isn't something someone can accidentally do.