As a case study, I did most of my grad work on solving Bayesian inverse problems using probabilistic programming for applications in engineering, which is pretty cross-disciplinary. I now work mostly in ML, but I didn't really even touch anything in the ML domain until after I finished school. I could have, the courses were available, but they just weren't relevant to me at the time.
Which largely counts as strong Linear Algebra and Probability Theory background.
CS only comes into the picture at runtime. ML theory is divorced from computability until then.
You don’t need a professional license to do math. Lots of computer scientists to harder and more interesting mathematics than their peers in the math dept. In that respect at least, the main substantive difference between the fields is about $40k/yr.
You're just stating things without justifying them.
The same can unfortunately be said of many "statisticians", who use statistics as a big recipe book without understanding the first thing about the mathematical underpinnings of the topic.
Don't believe me?
Go ask the first statistician you run into to give you a half decent of how the Chi-squared distribution and the Chi-squared test works, see what happens.
- Probability math is confusing and difficult, and a base understanding is required to use PPLs in a way that is not true of other ML/DL. Most CS PhDs will not be required to take enough of it to find PPLs intuitive, so to be familiar they will have had to opt into those classes. This is to say nothing of BS/MS practitioners, so the user base is naturally limited to the subset of people who studied Math/Stats is a rigorous way AND opted into the right classes or taught themselves later.
- Probabilistic models are often unique to the application. They require lots of bespoke code, modeling, and understanding. Contrast this with DL, where you throw your data in a blender and receive outputs.
- Uncertainty quantification often is not the most important outcome for sexy ML use cases. That is more frequently things like "accuracy," "residual error," or "wow that picture looks really good".
- PPL package tooling and documentation are often very confusing and don't work similarly to one another. This isn't necessarily the developer's fault, this stuff is hard, and the people with the domain knowledge needed to actually understand this stuff often have spent fewer hours in the open-source trenches.