Issue calling MATLAB from other programs, namely Blender via the MATLAB Engine for Python.

I have something of an unconventional setup in which I have the MATLAB (R2021a) Engine for Python installed for the Python install that's bundled with Blender. In this particular case, that'd be Python 3.7.4 for Blender 2.83.13

I can have an active MATLAB session running (with its engine shared!) and connect to it easily via Blender's Python console:

import matlab
session_id = matlab.engine.find_matlab()[0]
eng = matlab.engine.connect_matlab(session_id)

The above works just fine. If, however, I want to kick off another MATLAB session with the following:

import matlab
eng = matlab.engine.start_matlab()

Blender freezes up, regardless of any whatever additional arguments are passed, e.g. "-desktop". I've had no issues in the past here with R2019b, specifically.

This may warrant another post altogether, but it feels related.. I'm also attempting to use NVIDIA's NSight Systems CLI (https://docs.nvidia.com/nsight-systems/UserGuide/index.html) to profile various MATLAB tasks on a Linux machine. A derivative such bash command may look like:

/usr/local/cuda/bin/nsys/ profile -o "report.qdrep" /usr/local/bin/matlab -nodesktop -nodisplay -nosplash -r "disp('testing, testing'); exit;"

For R2021a, I get a similar sort of behavior. The nsys profiling seems to start, a MATLAB process appears to be running, but nothing gets printed to stdout/stderr as I'd expect. For comparison, running that exact same bash command but pointing to a MATLAB R2019b install, I get the typical MATLAB printout fed to stdout that I'd expect, where it prints the version information, copyright info, runs my typical startup.m script appending a few paths, and then the simple display() command is issued and the MATLAB instance exits.

Again, not at all sure these two situations are related. The first is performed via Blender on Windows 10 machine, and the second on a Linux CentOS 8 box..

Thank you for any insight!