It's a great question for the thread but probably in response to the wrong comment chain. But since we're here: it'll depend on your provider, just like v4. Some won't offer it at all, some will charge, some will force you to buy the "business" connection instead, some will use a static WAN and route the rest to you, some will use a dynamic WAN and route the rest to you, some will require their modem be used (and some will even 802.1x auth it), some will let you directly put it to your own gear.

The story isn't any different, there is nothing about IPv6 that changes this dynamic other than you have the additional option to use PD. What may be different is what your ISP requires you to do/purchase - by the sounds of it likely trying to push you to a business account which is a revenue tactic not a technology limitation.

As far as NAT with a dynamic IP to private v4 it works the same as NAT with an IPv4 connection with RFC 1918 space internally.

As for your performance issues with NAT you shouldn't see any latency with NAT on a network device, if you're using software routing on a Linux box or something try a standard hardware network device for the edge NAT instead as the data path for hardware devices is the exact same for NAT in those as it is for normal routing, in fact normal routing is normally just implemented a special case of NAT where the inside and outside addresses of the NAT are set to the same value. If you're currently using such a device for your edge NAT and experiencing problems with it either the device is broken or something is misconfigured as like I said everything is always "NATed" through such a device so it doesn't make any sense it'd have higher latency with certain internal IP values.

But seriously for home use without NAT look at PD, for business use with static routing and statically configured devices behind that routing look at what your ISP wants to sell you and see if you can call them on their crap but to be honest if you're running VOIP the business service is probably worth it anyways as you can get them to honor voice QOS through the oversubscribed local node into their backbone. If you go this route the IP space itself is the same as v4, you can either get it from your ISP or you can get it assigned to your LLC or whatever via your local RIR - literally anyone can get a /48 block assigned to them this way, maintenance fees for the allocation are the same as v4 but the RIRs actually have the space itself for free unlike v4 where you have to buy addresses and pay the maintenance fee.

You can tunnel if you want but I really wouldn't recommend it for VOIP. The same options you have for IPv4 VPNs are available for IPv6 and the setup is no different beyond the address type. There is also the option of teredo or 6rd but again I wouldn't really bother with them at this point in the game, they were intended for deploying v6 prior to its availability in ISPs not for this use case.

But the general idea is there is nothing about IPv6 that changes the way static addresses, static routing, or static allocation works beyond the size of the address field. That doesn't mean your ISP is choosing to give them to you at a reasonable price but it's not because of IPv6.