I don't really think that's the correct section that decides if element is clickable or not. But since you're confident here, I'll assume it as correct for now.
After line
move-result p2
Write this:
const/4 p2, 0x1
Try it out. Replace it with 0x0 & try again.
If it doesn't work, then wrong point.
To actually find out source of a button, I'll recommend using some frida script to log clicks & the calls that click event triggered, or use SimpleHook LSPosed Module, as it has that hook inbuilt.
If it isn't clickable, or if you want to dig statically, then:
I'll recommend to use "Developer Assistant" from play store, & find out the button ID.
If they're obfuscated for some reason, then search for the button text string on res/ and note down the ID of that instead.
After that, you're suppose to look for id's address. Search for it in res/value/public.xml and note down the address which should be in format of 0x7fxxxxxx . Find the address on smali code & the class that calls for it, those should be the class that initializes the button, and from there you should be digging the code.
You must call that button resource to make it clickable/unclickable, for example look for setEnabled call around it.
Reference, try compiling the code with ProGuard obfuscation is turned off and analyze the smali code:-
https://www.geeksforgeeks.org/how-to-enable-disable-button-in-android/
setTextInputLayoutFocusedRectEnabled
sounds more like an "style option" without an effect of the ability to focus a field or not. It is just if there is a rectangle drawn if the field is focused.