I suspect the answer from most people not on the forums would be 'we like Thameslink, we just want it to work.'
The data from Huntingdon and St Neots suggests that this is prioritising the few to the disadvantage of the many. Most Huntingdon and St Neots passengers do not use Thameslink to go beyond St Pancras.
In both cases the biggest London flows are still to Kings Cross and St Pancras, not into the core (110730 and 158649 for Huntingdon, 84649 and 81479 for St Neots).
And the next biggest are local: for Huntingdon. Peterborough (128589) is bigger than all of Farringdon-London Bridge (108742), and for St Neots, Huntingdon+Peterborough (108215) is bigger than all of Farringdon-London Bridge (96041).
The local traffic is especially disadvantaged by Thameslink disruption, often caused by events far away.
Between Bedford and Corby the local flows are important too, the biggest are:
57321 Bedford-Wellingborough
39413 Wellingborough-Kettering
34151 Bedford-Kettering
31923 Corby-Leicester
26656 Bedford-Corby
25400 Kettering-Corby
Those passengers are not going to be impressed if they were relying on a Thameslink service that disintegrated frequently, especially those trying to travel between Corby and Leicester.
You are right that people want Thameslink to work, and up to now it doesn't work anywhere near frequently enough.
It's not about distance alone, or even journey time alone, but also where the services sit in the overall service pattern structure, the potential for contra-direction flows, and the available infrastructure.
One of the causes of poor performance is that is that the Thameslink network is too complicated, and includes too many routes. The relationship isn't proportional, but every extra mile in the Thameslink network is another mile where the OHL can fall down, a rail can be broken, a signal can fail, a set of points can fail, or, sadly, where someone can go under a train.
One of the ways to make Thameslink work better is to improve resilience by simplifying routes and reducing risk. When in a hole, stop digging, and adding Corby (or Sheffield) to Thameslink would be more digging.
So I think there are pros and cons. As somebody who uses Thameslink trains regularly I value the direct link to the Elizabeth Line via Farringdon, the ability to reach central London and the River Thames without using the tube, and being able to travel to Gatwick AirPort directly. If however stations from Arlesey northwards lost this service then as long as interchange facilities at places like Hitchin, Stevenage, or Finsbury Park were provided without significant time delays I think it wouldn’t be too much of an inconvenience.
You are right that there are pros and cons. Other things being equal, over short distances the pros outweigh the cons, but as distance (or time) gets longer, there is a tipping point where the number of users of Thameslink connectivity has declined, and the performance risk has increased. Experience since 2018 suggests that the tipping point is about 50-60 miles and 60-75 minutes from the core to the extremity, which is Bedford, Cambridge and Brighton. I can't see that the pros outweigh the cons for Corby or Sheffield.