Hey @Stephanie-OG,
a quick designer insight and why this might be happening.
The bold and italic options in any text tool (Rich-Text, MS Word, Google Pages …) are just imitating a bold, italic version of a font.
As most people are not designers or simply don’t care about pixel-perfect font settings, the “bold”/“italic” button kinda solves the “problem”.
But once you really dive into typography, how fonts are getting designed and what an immense amount of work it is to put out a great font, you’ll quickly realize that these two options are not real bold/italic versions of the font.
Just a little comparison:
The same font (Roboto Medium),
the black one is “italic button” version, the red one is the real italic version of it
While those differences in this case might be somewhat neglectable, it’s exactly those differences that might change the whole appearance of a website, printed file… And this is why any designer is having a heart-attack when the customer tells him “Can’t you just click the “i” button to make it italic”?
And this is what I think is happening in this case.
Since you’ve uploaded proxima nova with Bold and Italic versions, HubSpot might deactivate those features in the RTE. I’m could imagine, because there might have been a designer involved who told the devs that it’s a big “no-no” to have a bold type and make it “bold” or having an italic font and making it “italic”.
I’ve tried Roboto in MacOS Pages (something I haven’t used in years).
If I click the italic button, it automatically changes the font style to the italic version of it. Same with bold… Might be different with MS Word, but since I don’t have it, I’m unfortunately not able to test it.
Besides this, Proxima nova is available as an Adobe Font.
I’m pretty sure that you have a few reasons why you’re implementing it as it’s stated in the docs - to be honest - I’ve never used it.
On one hand, I’m oldschool and I don’t want to over-engineer stuff.
On the otherhand I don’t want to put design desicions in clients hands 
The way I’m implementing custom fonts is a different one than the docs (the good oldschool way).
- If the font have some sort of embed code like something like Adobe Fonts, I’m putting it into the base.html or theme.css. If it doesn’t, I’m uploading the ttfs, otfs… to file-manager or design-manager.
- Adding @font-face rules to the CSS if they dont have an embed code.
- Adding CSS styles for bold, italics etc. so it’s easier for the client
- Providing custom RTE modules without font selection and depending on use-case a lot less options
- When a RTE is not required (Headlines, buttons …) im using simple text fields and - depending on use-case of it adding predefined styling options in the content or style tabs
I know it’s often an immense amount of work, but you might want to think about it 
best,
Anton