This is understandable, but what about P2SH addresses for deposits? Right now clicking on "New address" generates a P2PKH address, is it possible to start generating P2SH SegWit addresses instead? This could help to lower withdrawal fees, since it's a hot wallet and those coins are likely to be used for withdrawals later.
This only affects withdrawals to other P2SH segwit addresses, not withdrawals to legacy (both P2SH and P2PKH) addresses.
The fees for withdrawals are based on average transacion size and are calculated before you enter an address, they are the same regardless.
A switch there would need a complete overhaul of the withdrawal system, which isn't very cost/benefit efficient when bech32 addresses are just around the corner.
As said, a switch to segwit based address handling should be discussed, but I don't think it should be rushed and done right now,
I however do think the time for it is with a well designed and tested update when the bech32 standard is established.
As for bech32, it can be done optionally, for example you could put a checkbox like "generate bech32 addresses for deposits" somewhere in Settings tab, so it won't be too distracting and confusing for less experienced users.
Not with the current version of Core, nope.
P2SH is still standard for SegWit addresses and afaik bech32 is currently only partly supported, making it impossible for CG to utilize it right now.
Also, would Crypto-games accept my deposit today if it will come from bech32 address?
CG isn't the only service and many users send withdrawals directly to deposit addresses from other services.
While it isn't best use practice, we gotta acknowledge that people are doing this, and we gotta account for it when making decisions.
