Depends on your connection.

If your connection to your ISP is direct link or P2P, I dont see the need to use it.

However if there is a multiple-hop between you and your ISP (i.e. MPLS) you can consider using it.

My experience with GRE (in order of implementation);

1. I use it heavily in MPLS

- From main to ISP using eBGP.

- From production to disaster recovery sites using iBGP and OSPF.

- From main office to multiple sites using static and OSPF. So I don't have to pay service charge to MPLS provider whenever I need to add a new network/subnet to route. I control the routing.

- Actual failover tested.

2. I use it from main office to overseas remote sites with the following;

- Internet as primary (because its cheap) with IP GRE over IPSEC

- ISDN as backup with IP GRE over IPSEC

- Actual failover tested

Anything that has multi hop that bothers you, use Cisco router and implement IP GRE

You can be creative how to use IP GRE to your network benefits (and cost saving). I don't see any problem with IP GRE, the DF problem can be fixed by a single command line.