It’s a good point and as @ekohl also notes most hooks are short, minus the occasional upgrade related hook that generally ends up unpredictable time wise. I do think there is an argument to be made for showing users that something is happening (i.e. progress) to prevent a feeling of “is this thing stuck?” and gauging somewhat where the process is at. I added a screenshot of another “progress” style where we can show number of steps left in a stage and still show runtime.
A suggestion from @Marek_Hulan has been to indicate a number for each stage and how many stages are thus left. Something akin to the left side here:
[1/7] Warming up: (1/1) 00:00:00
[2/7] Executing boot hooks: (5/5) 00:00:00
[3/7] Package versions are being unlocked: (1.0/1) 00:00:01
[4/7] Executing pre hooks: (3/3) 00:00:01
[5/7] Configuring system: (700/700) 00:00:19
[6/7] Executing post install hooks: (5/5) 00:00:19
[7/7] Package versions are being locked: (1.0/1) 00:00:200
* Foreman is running at https://foreman.example.com
* Login credentials -- username: admin, password: changeme
The full log is at /var/log/foreman-installer/foreman.log
Assuming we can calculate that completely at boot time.