The issue is that this approach is almost guaranteed to produce basically untestable code with a myriad of invalid/nonsensical/completely broken input combinations, and its impossible to refactor, too, because you don't even know which parts of the parameter space are actually ever needed, or even how they are supposed to interact.

Whenever function semantics need to change, everything degrades further because of refactoring uncertainties (=> you end up with even more parameters).

This will also be extremely resistant to optimization because even finding the "happy path" is non-trivial.