After reading the pause/resume documentation at https://docs.oracle.com/middleware/11119/wls/JMSAD/troubleshoot.htm#i1129131, it looks like (a) the config bean fields you modified are not dynamic, and (b) regardless, they don't take effect regardless until the JMS Server is restarted. In general, a change to any non-dynamic config bean attribute requires a restart of the affected service(s) to take effect.
In short, if you want to change pause/resume state without restarting your JMS Servers, then the configuration beans aren't going to help. Instead, you can use the similarly named operations on the JMS runtime mbeans. If I recall correctly the console provides access to the runtime beans on its monitoring/control panels, and you can also call them from WLST or Java. Here's the JMS Server Runtime mbean and JMS Destination Runtime beans javadoc:
Note that a runtime bean change to your paused state is lost once your JMS Server restarts. So if you pause a destination via the runtime bean, and want to the destination to stay paused after a restart, then you also need to set the corresponding config mbean setting...