Sorry, but we are not familiar with these details. The connection should be entirely managed by the IBM MQ client library (with the help of the JDK).
As far as we know, TLS_RSA_WITH_AES_256_CBC_SHA256 is among the cipher suites currently enabled by Java, still in Java 17.
Can you see other Java clients that connect successfully?

BTW, your previous problem was about the certification path.
This new problem seems a step backward, because the cipher suites are negotiated before.
What evidence do you have that the issue is that the TLS_RSA_WITH_AES_256_CBC_SHA256 cipher suite is missing on the client side?