Two points:
#1) For the actual topic of this thread, we have this in the blocklist for the device settings (i.e. kiosks):
google.com
yahoo.com
bing.com
duckduckgo.com
tiktok.com
facebook.com
yandex.com
baidu.com
discord.com
youtube.com
ask.com
search.brave.com
along with "accounts.google.com" (without quotes) in the exceptions list. This prevents people from finding a way to navigate to most search pages and social media links, which are the primary means of exploiting the kiosks.
#2) @sundermannc thanks for your post and video link. I heard about this hack before but dismissed it when the data:// method didn't work for us, but the html code method worked just fine. We have also put in the chrome://extensions block for now.
In case anyone else is wondering, we tried just blocking the direct URL of the extension itself so that we didn't have to block the whole extensions interface. While the block works when going to the link directly, if you just navigate to the extensions management screen (chrome://extensions) and click on your filter's extension, it ignores the URL block until you refresh the page (... and then the browser crashes, lol).
We submitted a support ticket to our filter vendor (Linewize).