Technically, there's no requirement for a prefix to be bound to the interface. The RA will be sent from the lladdr, and nodes will build routes using that lladdr as the destination. NDP ("arp") works just fine with lladdr's - it's a link-local process after all.
Looking at my own Cisco router, there have been provisions for announcing "unbound" prefixes for a long time:
gw-1(config)#int g0/0
gw-1(config-if)#ipv6 nd ?
advertisement-interval Send an advertisement interval option in RA's
autoconfig Automatic Configuration
cache Cache entry
dad Duplicate Address Detection
managed-config-flag Hosts should use DHCP for address config
ns-interval Set advertised NS retransmission interval
nud Neighbor Unreachability Detection
other-config-flag Hosts should use DHCP for non-address config
prefix Configure IPv6 Routing Prefix Advertisement
ra Router Advertisement control
reachable-time Set advertised reachability time
router-preference Set default router preference value
gw-1(config-if)#ipv6 nd prefix ?
X:X:X:X::X/<0-128> IPv6 prefix x:x::y/<z>
default Specify prefix default parameters
framed-ipv6-prefix Advertise prefix obtained from RADIUS server
HOWEVER... given a Standard LAN is commonly /64, there's very little reason not to assign an address for each prefix to the interface.