It seems like it would be best to separate gas_per_second and minutes_per_epoch into independent variables first, before making changes like this. That would allow us to make changes to things like slot time without having to simultaneously touch state growth, average bandwidth, or finality times. Each of those variables could be changed/updated in their own respective EIPs and discussed independently from a change like this.
The advantage of such an approach is that concerns like average bandwidth use, finality time, and state growth can be ignored and instead discussion can focus on things like propagation time between stakers, attestation collection timing, etc. which are all directly related to slot times.
This change would increase the max state growth rate by 50%. While there are steps being taken to limit non-state storage growth requirements, state growth is permanent and perpetual at the moment with no way to cap it. Until this unbounded growth problem is addressed, it seems prudent to avoid any significant gas limit increases.
At Ethereum’s current growth rate, it has already pushed many (I believe almost all) home node operators out of the market, and as storage requirements continue to grow more and more home operators are pushed out. Even running in a datacenter is getting more challenging as large-disk servers tend to be much more rare and much more expensive than high CPU servers.