I am going to use a car analogy.
Who cares about sequential read/write (max speed you see on speedometer on a car). You should be comparing Random read/write speeds.(horsepower of a car)
Aren't both important? Sequential reads and write if you are reading loading large files or programs or writing large files, and Random reads and writes if you are doing smaller everyday reading and writing.
We are trying to encourage Apple to innovate and use the best practices for all users (including Pros and Creators), so having fast SSD drives/chip configurations that benefit Pros and regular consumers alike is the ideal model as far as SSD drives/chips are concerned. People are usually willing to pay an extra $10 or $20 or even more for superior all around performance gains.
Since the SSD drive is so important for both storing data and programs, and also serving a swap memory drive, it makes sense that the faster the better is preferred for both Sequential and Random read and write SSD speeds. Swap memory speed and size is often overlooked, as many people do not even realize that memory swapping is happening, when they have lots of Chrome tabs open, and are running many CPU and memory hungry programs at the same time.
It is ridiculous, in my opinion, that the 512GB MacBook Pro M2 Pro and 512GB MacBook Pro M2 Max models have slower SSD sequential read and write speeds than the prior 512GB MacBook Pro M1 and 512GB MacBook Pro M1 Max models released in 2021, not to mention slower than the 1TB or larger versions of the same MacBook Pro M2 Pro and Max models.
You never shortchange a Pro customer in performance, if you know what is good for you, otherwise you experience the backlash, and customer disappointment, like we are now seeing concerning this SSD speed issue. This violates Marketing 101 to keep your customers happy, so you increase customer goodwill, and will receive positive word of mouth recommendations from your customer to others.
The best video that deals with this slower SSD issue from a marketing and customer disappointment issue is this: