@NickBeam27 Those are different categories, yes, though in your case they're both doing the same thing, cooking.
The people that design matchmaking systems aren't in the same department, the amount of people in that department might even be lower than the amount of designers.
That would mean that it would take longer for them to come up with a proper matchmaking system, especially because it has to be tested on a large scale to produce results.
After they create a model for matchmaking, they'd still have to implement it, meaning that code has to be tested too, which in the end would be quite the project.
Both the design and coding departments in this situation have other things to work on, the ranked system for example, which might even take priority now.
The design department in charge of characters, weapons, lore and so forth isn't limited by needing it to function fine. (As it just has to looks good, there is no functionality like a matchmaker or code that would need to be made to it work)
They are of course still dependant on other departments, like motion tracking, writers and so on, though these departments typically don't run into the same issues like the departments I mentioned previously.
They don't need to do extensive testing, all they need to do is make sure it looks good, so realistically we'll be seeing more cosmetics pushed out than changes to matchmaking systems.
Logically, this is to be expected, more content will come from the other because it's easier to produce said content.
Now, if this is the exact case, it would mean that they'd have to stop making cosmetics for a while to slow down overall production so it looks "fine" again.
Do note that they're still a company, their business model revolves around micro-transactions, their internal structure will obviously focus on the design of skins, emotes and all that.
You can't just say a single department reflects on other departments that are not affiliated to that other department, I personally find that lacking logic.