Speaking for myself only:
What would the value to most people be for more context about performance issues within the change list with the way that Epicor is positioning point updates (no breaking changes to RDDs, UI customizations, BPMs, etc)? If someone is on a point update on a given release, Support really does expect our customers to apply the latest point update in their testing environment at some point to determine if the latest point update resolves the issue (ideally for all involved before submitting an issue as that will really save our customers time–if it is addressed in the latest update, then you don’t even need to open a case with Support as that is the solution to issue).
If someone has performance issues in 10.2.200.x with a process where we have listed we’ve done some work around that process in 10.2.200.y, why wouldn’t one just apply the update in their testing environment and test to see if it has an impact? If not, then, one would have to submit a case to Support for us to review if it was a concern for the user.
If someone has a performance issue in 10.2.100.x with a process listed in the change list for that process that was changed in 10.2.200.y, I would still recommend upgrading the testing environment to that release/update, but, if more context was needed, a Support case could be opened to determine if there would be any impact–though, one of the first three things out of Support will be “have to tested to see the actual impact?”
I guess my broader point is that for updates within a release (10.2.200.x to 10.2.200.y), if someone wanted to know if Jira/SCR XYZ included in 10.2.200.y would have any benefit for their usage, the best (arguably the only) way to know is to actually apply it and test–more context around the issue wouldn’t actually validate whether or not it would help or not with absolute certainty.
If someone has a need for more information for a specific change than what is included in the change list, contacting Support would be the only way to get that information. This isn’t to say that Support can always provide more information.
EDIT: As a Support resource I should say that I do not have direct control over what or how much data is provided via this process, so even if there were really good reasons to include more info that would benefit the majority of customers, all I could do is advocacy.