One suggestion is to avoid an off-by-one error, which could lead to misunderstandings when interacting with the system. However, there's an openness to accept a minor level of confusion if it means there will be fewer restrictions on the nSequence of the coinbase transaction. An alternative approach mentioned involves encoding the height within the nVersion of the coinbase transaction. This method would provide a simpler way to access the block height than parsing the scriptSig. Nonetheless, if the goal of making the block height easily accessible is not prioritized, a requirement for the coinbase transaction's nVersion to be set to any value except 1 might suffice. This conversation underscores a balancing act between enhancing usability and maintaining flexibility in the system's design parameters.