Ultimately, anything your webpage is loading will be visible to the inspector because it is publicly loaded. Think maybe more in terms of obfuscation than actually hiding. Loading element through js, using json packets, etc.. Can make understanding the code displayed in the editor much less inticing to understand.
Look around at the code for some larger sites that have advertising programslike facebook or linkedin. These companies have very large incentives to make their data publicly displayed in a manner which makes scraping difficult. They market access to their data, so it hurts them if others are able to access it in a prifitable manner, such as large scale scraping. For this reason, almost all major companies no longer offer public apis, and now reqhkre the registration of 'apps' for data access. Now, all this data is still needed for public display, so hiding isnt an option. If you look at someones fb profile, it is very easy to understand visually. However, fb uses a lot of dynamic css generation which makes it a nightmare for people trying harvest data from them.
Ultimately, as matt cutts has been quoted saying, you have to break the spirits of people who behave in a manner in which youd like to avoid. If your data has to be made public, as is often the case with websites, make it obscenely hard to sift through for those who are trying to rip you off and theyll probably just move along to the next guy.