There are a few things I see here to consider.
1) Is the problem that you don't have enough people or that they are too narrowly skilled? Both result in the "shared resource" problem, but require very different solutions. For example, not having enough people can be solved by either hiring more people, cross-training many of the basic skills in that discipline, and providing coaching and mentoring from the expert (the designer). On the other hand, if the problem is that all they are capable of doing is a narrow set of design tasks then they may need some cross-training to be able to effectively integrate into the team.
2) Why don't you want "shared resources"? This isn't the end of the world. If you have it for a while, that may just be life, but it can create problems so you don't want to force this or let it linger too long. There are two main problems with "shared resources". The first is that these skills are usually important and you lose a lot of time to overhead with this model, so you get less and less of an important skill as you spread them across more squads. Second, what happens the when two squads need the same person's time to move forward? Now someone has to lose. This will probably result in holding up a whole squad or making them work on something less valuable while they wait. In the worst-case scenarios, I've seen this result in critical missed deadlines that cost hundreds of thousands of dollars. Those circumstances aren't common, so don't panic, but that's why you don't let it linger.
3) Do you need extreme depth in this skill. Are you doing something bleeding edge in the industry. Companies like Tesla or Boston Dynamics (electric self-driving cars and walking autonomous robots respectively) need people who are very narrowly focused in their skillset because they need all of their time dedicated to a deep understanding of a specific skill. 99.9% of companies don't need that. If you're in that 0.1%, the value added by narrow, deep skills is way more than the value lost or risk added by the "resource sharing" model.
4) Where are you at now? There's a big difference between acknowledging that this is where you are at now and deciding to stay there. If having shared UI/UX designers is where you are at, don't beat yourself up over it. If it's not where you want to be in a year, talk about your plan to grow on to a different circumstance.
Hope this helps - this is really a situation best suiting to coaching and I tried to turn a coaching conversation into a post, which is always messy at best. At the very least, I tried to give you some angles to look at your situation from to make the most effective decision.