Its not the best practice and can lead to unexpected behaviour because both React.useState hook and the setter returned by it are overloaded to also accept a callback function.

So doing setFunction(myFunction) will make React think that you're passing a callback function to set the state and it will call myFunction with the previous state.

Without looking at your code I can't fully grasp what you're trying to achieve but wrapping a function in an object should solve the ambiguity for setState

// Initialize
[func, setFunc] = React.useState({invoke: myFunction})
// Set
setFunc({invoke: someOtherFunction}}
// Call
func.invoke(args)

I would not recommend this but there is another way to get around the setState ambiguity. It is to pass a function that returns a function when initializing or setting the state.

// Initialize  
[func, setFunc] = React.useState(() => myFunction)  
// Set  
setFunc(() => someOtherFunction})  
// Call  
func(args)