They seem naturally sequential and an imperative to me.
I can't imagine how a list of instructions would be clearer in haskell.
cook meat sauce = do
pan <- getPan
addTo pan meat
cookFor pan 10
addTo pan sauce
cookFor pan 3
food <- contents pan
pure foodAlthough written in an imperative style and thus superficially similar, the haskell differs in that it is referentially transparent.
I think that makes it objectively clearer, because it implies certain guarantees that nothing will surprise the reader.
It is not at all obvious that this is truly the case. If it was the case, why didn't humans intuitively develop mathematics from a computational foundation? It took centuries before we made the leap from mathematical abstractions to Turing machines, and the two are (in some great general sense) isomorphic.
So, you are right regarding the mindset of human philosophers, but that is not the sort of problems OP's students were tasked with solving.
I've taught Haskell at an university and almost none of the students ever found the model of computation natural. I think we humans simply find following a series of steps easier than reasoning in an abstract mathematical sense.
That being said, I absolutely see the value of the latter, and consider it a good thing that functional concepts are gaining popularity in imperative languages.