Users might see it as a good thing to have yet another feature, but this sort of type-softness is why Excel is bad. In general having every feature is a bad thing, you need constraints to design things, to have idioms.
Making everything flexible is what allows you to make spaghetti that nobody understands.
Excel does not need to be as opinionated or portable as a programming language. This might actually be a lesser of two evils considering what type of user behavior it encourages. (I've heard a similar ethos behind certain design decisions of Go)
Microsoft is actively harming the laypersons comprehension of their data with 'features' such as this.
Reasoning about the basic shape of data with real estate managers using the Btrieve[0] database on DOS (and then XP) in years gone by was noticeably more straight forward than wrangling the monolithic excel monstrosities encountered today.
I shall embark upon a quest, and the quest’s object shall be thus: to define multiple lambdas within a list, and thereupon, to make cells downstream depend upon the lamda’s, and to make them in turn become lists or values, and so on, until the whole thing breaks.