@franktech Not exactly sure what you mean by “import Inputs at runtime”.
Its easy enough to redirect / override existing inputs via a well placed Enable/Disable Input node.
The only immediate issue in doing this is that the input is not replicated to the server.
@Syed The same thing could be used to ignore/stop ignoring a particular input too.
To ignore the action, enable input for the local player controller and consume then a the input you want to ignore.
When done, disable input for the local player controller.
I actually created something similar to what you describe - Listen for Input Action & Stop Listening for Input Action.
I might be able to change that to be compatible with a Blueprint function library… in which case, it could be added to Rama’s function library.
If you (or anyone else for that matter) are interested, let me know and I’ll see about getting it converted and add a pull request to Rama’s function library.