First, you seem to have dropped the percentage topic, which you had initially talked to. It seems like you're just changing the topic for the sake of arguing something on a tangent (isn't that against the rules here).
Now you seem to be talking about people who are too good to do things. Which is entirely different than what I'm talking about - appropriately staffing a team based on expected tasks and minimizing budget.
Tasks are not really "junior" or "senior" tasks but really tasks that juniors or seniors could do with different results in terms of time, cost, quality, etc.
Sometimes a "junior" is more experienced at the latest methods. This is one thing you see with medical doctors or electrical engineers, that many people go through their careers and keep using the same methods they used at the beginning. (Think of the old saying that "Science advances one funeral at a time")
For instance 20 years I go didn't expect an undergraduate student to have any idea what version control is, today I expect them to have a Github account.
You are putting words in my mouth. I never called the tasks "junior" or "senior". Looks like you agree with me, but felt the need to argue anyways.
The data scientist who thinks he is too good to check his notebooks into version control is just one version of people who think they are "too good" to be doing what they are doing.
In small teams people do the work that is critical whether it is too "easy" in their estimation or if they have to stretch themselves to do something difficult. Sometimes they need to get help. A few people on the team can indulge in doing only the work they feel like doing, but that's because there are adults on the team who cover for them.
There are many advanced programming tasks which could, in principle, be assigned to some juniors. For instance, CS majors usually take one or more courses in compilers and programming languages. If your organization is dependent on a legacy programming language you could possibly get one of those juniors to write a transpiler that compiles it to something current. Succeeding at that takes some guidance, but it might take some form that some "seniors" would find offensive such as writing a really tough set of unit tests.
Many "seniors" on the other hand never took any compiler courses or sold their textbooks and forgot everything 10 years ago.