Traffic capture struggles with speculative testing in general,
and can't account for new functionality that doesn't exist yet.
The biggest blocker is that most traffic is highly sensitive to the environment. For example, UUID's and ID's likely don't exist in the development environments where you really want to test ahead of feature release--generally the datasets won't be the same. If they are the same, you'll complicate your life GDPR wise, increase your risk of breaches, and risk sharing PII.
Rather than capture traffic, you can get a similar accuracy, and more flexible setup, by looking at the traffic patterns and allocating your load based on transactions proportionally.
The biggest blocker is that most traffic is highly sensitive to the environment. For example, UUID's and ID's likely don't exist in the development environments where you really want to test ahead of feature release--generally the datasets won't be the same. If they are the same, you'll complicate your life GDPR wise, increase your risk of breaches, and risk sharing PII.
Rather than capture traffic, you can get a similar accuracy, and more flexible setup, by looking at the traffic patterns and allocating your load based on transactions proportionally.