Sometimes you need to take a step back and look at your code from the point of view of an organization with a wide variety of developers of different skill levels and time. The point of good code is not always to be clever or even composable. Some of the best characteristics of good code are simplicity, readability, and being concise.

You should be able to hand this code to any of your peers and they should be able to work on it quickly. That is just not what I'm seeing with this code. You can claim superiority or genius or experience as to why it's written this way, but the practical truth of programming is that we have new developers coming into organizations constantly. The practical truth of making money as a company is that code should read like a book. Your final lines are somewhat readably, but your implementation is not readable. Destructuring would definitely help.

In the end what is the point of functional programming if you're just falling into old habits of passing around messy objects like ...options?