If you don't want to use a function, I suppose you could embed the code for something like DelimitedSplit8K or an XML splitter (if ordering doesn;t matter) in your code....

Then your only method is Dynamic SQL. With a large amount of data, this WILL perform poorly, as you are having to refer to the table dbo.Profile for every Profile....

That white space is in your design view too; it's appearing as you've designed. You need to move the elements,

Then all the tables have the same definition? Then this design needs to ideally change. Have a Profile table which has the ID of the Profile; not 1 Profile table...

So wait, the columns are bespoke per table?

Only with Dynamic SQL. This, however, has the smell of bad data design. It might be better to take a step back and show us the set up you have,...

No, the only way to to make your query safe is to parametrise it. The documentation example covers how to parametrise your query.