Join to a Culture Table vs Select Culture ID
No need to refactor the single query into two separate ones.  SQL Server should be able to figure out the most optimal way to execute the query on your behalf.  Make sure the Culture table has a unique index on CultureTag and, in the case of a non-clustered index, add all of the columns needed by the query as INCLUDED columns.