Session Resumption will re-use the previously negotiated cipher spec, so if you need to renegotiate a different cipher, you will need a new handshake. To quote RFC 5246 section 7 (emphasis mine):
The Handshake Protocol is responsible for negotiating a session, which
consists of the following items:
...(session identifier, peer certificate, compression method)...
cipher spec: Specifies the pseudorandom function (PRF) used to generate keying
material, the bulk data encryption algorithm (such as null, AES, etc.)
and the MAC algorithm (such as HMAC-SHA1). It also defines
cryptographic attributes such as the mac_length. (See Appendix A.6
for formal definition.)
...(master secret, is resumable)...
These items are then used to create security parameters for use by the
record layer when protecting application data. Many connections can
be instantiated using the same session through the resumption feature
of the TLS Handshake Protocol.