Requiring the speed to be checked and reset should trigger the reassessment of the speed required according to the landing conditions - operational requirement EASA, recommendation FAA.
FMC might have the forecast wind, but not actual or gusts / turbulence, which could require a higher speed.
The FMC would not have runway condition or braking action (unless entered), which should also influence speed selection or at least speed or configuration management. Which in turn should trigger the need to adjust landing performance / auto brake selection. Also act as a cross check of landing weight against the expected or computed value.
A good triggering procedure should force engagement of thought, opposed to blind following of some computed value.
So not having a display of computed value might be better.
Just because something can be done is not always a good idea, or because it reduces workload; we often fail to consider both technology accuracy - reliability, and human performance in our choice of action