Another update: It seems the culprit was MKLSparse.
After changing using MKL, MKLSparse to just using MKL in my module, the issue appears to have vanished.
Apparently, the MKLSparse package has also faced other (related?) bugs recently.
I commented on their most recent issue discussing the bugs, was not sure whether I should open an issue myself.