To add to Guenter's response, and hopefully not to contradict, shall we think about how this works on a technical level.
You have your Web Services calls and System (Socket) calls for the same transaction, both metrics actually relate to the same communication just on different levels.
You won't see the same amount of responses per interval, average response times because sockets will not be opened and closed as many times as web service calls will be made.
I don't write these applications, but I would assume it would be best practice for a socket to be opened, then as many web service calls to be made as possible (really that depends on who is using the application) but perhaps you reach a socket timeout as there haven't been any web service calls for a while, so the socket gets closed.
Then when more web service calls need to be made, the socket will first be opened.
I assume it is not a good practice for a socket to be opened and closed each time a web service call needs to be made.
I hope this explains why there is not a 1:1 correlation between the metrics (Responses per Interval etc) for the two metrics.
You would see a similar relationship between JDBC calls and Socket calls to databases, and it is possible to see just the System calls as outbound socket calls to another system, but no other related metrics.