This issue is not reproducible as described here. It has been tested on multiple machines and on ArcGIS Pro 3.4 and 3.5.
Updating to ArcGIS Pro 3.5 may bring some relief since some of the notebook packages are updated, and a fix to the notebook integration that looked similar to this has been made.